MCP Search Server vs webfetch
MCP Search Server is an MCP server published by KazKozDev. Marketplaces we read that list it: 1 (Official MCP Registry). 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
| Marketplace |  webfetch | |
|---|---|---|
| Official MCP Registry | Listed Version: 0.1.1 No figure published Not marked · First seen |
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
| Fact | MCP Search Server | webfetch |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | No figure on GitHub | 59 |
| Forks (GitHub) (differs) | No figure on GitHub | 6 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp-search-server) | On your machine (webfetch-llm) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 4, secrets among them: 3 |
| Parts of the bundle (differs) | Not a bundle | 1 |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/kazkozdev/mcp-search-server | github.com/firish/webfetch |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen | 2026-10-11 | 2026-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
MCP Search Server
Web search, content extraction, PDF parsing, plus datetime and geolocation tools. No API keys.
webfetch
Self-hosted web search for LLM agents: search -> fetch -> rank pipeline with semantic caching
How to run each
MCP Search Server As a local MCP server: PyPI package
claude mcp add --transport stdio search -- uvx mcp-search-serverwebfetch As a local MCP server: PyPI package
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-llmRequires: 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 MCP Search Server publish no settings it asks for, so we do not compare settings.
What it can do: MCP Search Server · What it can do: webfetch · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.