Bing Search vs Google Custom Search MCP
Bing Search is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑17.
Bing Search is a plugin bundle for AI coding tools published by AusertDream. No marketplace we read lists it any more. Google Custom Search MCP is an MCP server published by A1-x-Tech. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-24. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |  Google Custom Search MCP | |
|---|---|---|
| Community marketplace ausertdream/bing-search-cli | Removed on 2026-10-17 Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 2 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.0 Downloads/month (npm): 328 Downloads/week (npm): 18 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | Bing Searchno longer listed · | Google Custom Search MCP |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 2 | 0 |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (github:ausertdream/bing-search-cli) | On your machine (mcp-google-custom-search) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 5, secrets among them: 1 |
| Parts of the bundle (differs) | 1 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/ausertdream/bing-search-cli | github.com/a1-x-tech/mcp-google-custom-search |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-14 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of Bing Search
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Web search and page extraction across several independent search providers.
-
Web search via SearXNG and/or You.com, plus clean Markdown crawling via Crawl4AI. Self-hosted.
-
Keyless multi-engine web search, fetch, and clean-Markdown read for AI agents. No API keys.
-
Web search and page reading for AI agents, including JSON APIs, RSS feeds and YouTube.
-
No-API-key web search, page fetching and document reading across many engines. Local-first.
-
Self-hosted web search for LLM agents: search -> fetch -> rank pipeline with semantic caching
What each says it does
Bing Search
Dual-engine (Bing + DuckDuckGo) web search and page-fetch MCP server. No API key, no rate limits, optional proxy.
Google Custom Search MCP
MCP server for Google Custom Search: web and image search via a Programmable Search Engine.
How to run each
Bing Search
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Google Custom Search MCP As a local MCP server: npm package
claude mcp add --env "GOOGLE_CUSTOM_SEARCH_API_KEY=<YOUR_GOOGLE_CUSTOM_SEARCH_API_KEY>" --transport stdio mcp-google-custom-search -- npx -y mcp-google-custom-searchRequires: GOOGLE_CUSTOM_SEARCH_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of Bing Search publish no settings it asks for, so we do not compare settings.
What it can do: Bing Search · What it can do: Google Custom Search MCP · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.