Bing Search API

io.github.saulius876-lgtmv1.0.0Updated Oct 3, 2026

Bing web search results for AI agents: title, URL, snippet, date. Replaces the retired Bing API.

VerifiedStreamable HTTPWeb executableWeb Search & Scraping

Overview

AI-generated overview

Lets an assistant run Bing web searches and get back titles, URLs, snippets and dates.

What it does
This remote MCP server exposes Bing web search to an AI assistant, returning result titles, URLs, snippets and dates. It is positioned as a replacement for the retired Bing API, so it is meant for straightforward query-and-results retrieval rather than advanced search features.
When to use it
Use it when an assistant needs current web results with source links and dates, for example to ground answers in fresh pages or to gather candidate sources for follow-up reading.
Requirements
It runs as a remote streamable HTTP endpoint at mcp.apify.com, so no local runtime or package install is needed. The manifest declares no authentication, environment variables or headers, but the provider is Apify and an account or token may be required in practice.
Before you install
The manifest declares no credentials, but the endpoint is hosted by a third party, so search queries are sent to that provider. Confirm any account, token or usage limits before relying on it, and treat returned snippets and URLs as unverified third-party content.

Installation

In SourceWeft

  1. Open Bing Search API in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "bing-search": {
      "type": "http",
      "url": "https://mcp.apify.com/?tools=sauliusautomatesit/bing-search-api"
    }
  }
}

Tools

0
Tool metadata has not been indexed yet.

Version history

1
  1. v1.0.0LatestOct 3, 2026