Ext Ops Panel
Open dashboard
Comparison

Bing Search vs webfetch

Bing Search is a plugin bundle for AI coding tools published by AusertDream. Marketplaces we read that list it: 1 (Community GitHub marketplaces). webfetch is an MCP server published by firish. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-14. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplaceBing Searchwebfetch
Community marketplace ausertdream/bing-search-cli Listed
Version: 1.0.0
No figure published
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.3
Downloads/month (PyPI): 102
Downloads/week (PyPI): 43
Forks (GitHub): 6
Stars (GitHub): 59
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

Bing Search vs webfetch
FactBing Searchwebfetch
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)No figure on GitHub59
Forks (GitHub) (differs)No figure on GitHub6
Last releaseNot publishedNot published
Where it runs (differs)On your machine (github:ausertdream/bing-search-cli)On your machine (webfetch-llm)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published4, secrets among them: 3
Parts of the bundle11
LicenceMITMIT
Repository (differs)github.com/ausertdream/bing-search-cligithub.com/firish/webfetch
Changes in the last 7 days22
First seen (differs)2026-10-142026-10-11

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

Bing Search

In its own words, on Community GitHub marketplaces:

Dual-engine (Bing + DuckDuckGo) web search and page-fetch MCP server. No API key, no rate limits, optional proxy.

webfetch

In its own words, on Official MCP Registry:

Self-hosted web search for LLM agents: search -> fetch -> rank pipeline with semantic caching

How to run each

Bing Search As a Claude Code plugin

Claude Code
/plugin marketplace add ausertdream/bing-search-cli
/plugin install bing-search@bing-search

webfetch As a local MCP server: PyPI package

Claude Code
claude mcp add --env "BRAVE_API_KEY=<YOUR_BRAVE_API_KEY>" --env "SERPER_API_KEY=<YOUR_SERPER_API_KEY>" --env "TAVILY_API_KEY=<YOUR_TAVILY_API_KEY>" --transport stdio webfetch -- uvx webfetch-llm

Requires: BRAVE_API_KEY (secret), SERPER_API_KEY (secret), TAVILY_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: webfetch · 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.

Where the data comes from: how the catalog is built