MCP servers · cloudcorprecords

bingdata: Bing search results as JSON via a HasData MCP bridge

A local bridge to a hosted HasData Bing MCP server that returns Bing search results as JSON through one read-only tool.

This text was machine-translated from the publisher's own information and has not been checked by a human editor. The publisher's original text is the reference.

This resource was imported automatically from the sources listed below and has not been reviewed by the AI Gate team yet. The description is the publisher's own, as published. Check the repository before installing.

What it does

bingdata forwards search requests to the hosted HasData Bing MCP server and returns the results unchanged. Given a query, its single tool, hasdata_bing_serp_getSearchResults, returns the organic results with title, URL, snippet, displayed URL and position, plus related searches. Where the upstream provides them, the ad block and the Copilot answer are included too. The bridge stores no results itself and exposes no write, messaging or payment tools.

It suits workflows where an MCP client needs Bing results in structured form. Searches can be localised by free-text place or by latitude and longitude, and narrowed by market, country, interface language, safesearch level, date filters, device type and result offset for paging.

It runs as a CLI that takes one JSON argument, as a stdio MCP server, or in Docker, where the default command starts the MCP server. The optional HASDATA_BING_MCP_URL variable overrides the upstream endpoint. The optional HASDATA_API_KEY variable, when set, sends the caller's own HasData key with each upstream request. Failures come back as error results whose text begins with "bingdata error:". The test suite runs against a stubbed upstream, with no live network calls. The project is released under the MIT licence.

Limitations and requirements

Requests are forwarded to the upstream endpoint, which defaults to the hosted HasData server. The HASDATA_API_KEY variable is optional; when it is set, the caller's own HasData API key is sent as an x-api-key header on every upstream request. Upstream errors, including isError flags the upstream sets, are returned to the caller as they are.

Safety

Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.

  • Runs code or changes an assistant's behaviour

Sources

  • Official MCP Registry first seen 13 Nov 2026 · last seen 13 Nov 2026 · its page on the source
    io.github.CloudCorpRecords/bingdata

    Bing search results as JSON: SERPs with the ad block and Copilot answer, geo and market targeting.

    v0.1.0
    As shown on registry.modelcontextprotocol.io when we last read it
MCP servers
cloudflare

Cloudflare MCP servers

Cloudflare's hosted MCP servers for its products: documentation search, sandbox containers, browser rendering, Radar internet data, logs and analytics, Workers and more.

4.5K GitHub starsCloud & DevOpsSoftware development
Updated 17 Nov 2026
MCP servers
redis

Redis MCP Server

Redis's official MCP server that lets an AI assistant store, read and search data in a Redis database, including streams, JSON documents and vector indexes.

642 GitHub starsData & databasesSoftware development
Updated 17 Nov 2026
MCP servers
microsoft

Playwright MCP (browser automation)

Microsoft's MCP server that lets an AI assistant open web pages, click, type and read them through a real browser, using the page structure instead of screenshots.

39.6K GitHub starsTesting & QAWeb, search & browser
Updated 17 Nov 2026
MCP servers
hashicorp

Terraform MCP Server (HashiCorp)

HashiCorp's MCP server that gives an assistant current Terraform Registry information on providers, modules and policies, and can manage HCP Terraform workspaces.

1.6K GitHub starsCloud & DevOpsSoftware development
Updated 17 Nov 2026