Ext Ops Panel
Open dashboard
Comparison

webfetch vs CN Scraper MCP

webfetch is an MCP server published by firish. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). CN Scraper MCP is an MCP server published by goesByhc. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-21. 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
MarketplacewebfetchCN Scraper MCP
Official MCP Registry Listed
Version: 0.1.3
Downloads/month (PyPI): 102
Downloads/week (PyPI): 43
Forks (GitHub): 6
Stars (GitHub): 59
Not marked · First seen
Listed
Version: 0.4.1
Downloads/month (PyPI): 385
Downloads/week (PyPI): 127
Forks (GitHub): 7
Stars (GitHub): 68
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

webfetch vs CN Scraper MCP
FactwebfetchCN Scraper MCP
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)59 (worse)68 (better)
Forks (GitHub) (differs)6 (worse)7 (better)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (webfetch-llm)On your machine (cn-scraper-mcp)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)4, secrets among them: 3Not published
Parts of the bundle (differs)1Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/firish/webfetchgithub.com/goesbyhc/cn-scraper-mcp
Changes in the last 7 days00
First seen2026-10-112026-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

webfetch

In its own words, on Official MCP Registry:

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

CN Scraper MCP

In its own words, on Official MCP Registry:

MCP server for AI agents to search major Chinese internet platforms with local-first login support.

How to run each

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)

CN Scraper MCP As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio cn-scraper-mcp -- uvx cn-scraper-mcp

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 CN Scraper MCP publish no settings it asks for, so we do not compare settings.

What it can do: webfetch · What it can do: CN Scraper MCP · 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.

Where the data comes from: how the catalog is built