Fetch (Reference) vs Web Content Extract Mcp
Fetch (Reference) is an MCP server published by modelcontextprotocol. Marketplaces we read that list it: 1 (Docker MCP Catalog). Web Content Extract Mcp is an MCP server published by varvararatta. Marketplaces we read that list it: 1 (Official MCP Registry). 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 |  Fetch (Reference) |  Web Content Extract Mcp |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:1a7a0996a565 Forks (GitHub): 11 787 Pulls (Docker Hub): 1 912 772 Stars (Docker Hub): 58 Stars (GitHub): 91 222 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.0 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 | Fetch (Reference) | Web Content Extract Mcp |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 91 222 (better) | 0 (worse) |
| Pulls (Docker Hub) (differs) | 1 912 772 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 11 787 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/fetch) | Remote server (web-content-extract-mcp.mcpize.run/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 1 | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | NOASSERTION | Not stated |
| Repository (differs) | github.com/modelcontextprotocol/servers | github.com/varvararatta/botfactory-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | not checked yet |
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
Fetch (Reference)
Fetches a URL from the internet and extracts its contents as markdown.
Web Content Extract Mcp
Web Content Extract Mcp connects AI agents to real public APIs via MCP. Tools include
How to run each
Fetch (Reference) As a local MCP server: Docker image
claude mcp add --transport stdio fetch -- docker run -i --rm mcp/fetchWeb Content Extract Mcp As a remote MCP server
claude mcp add --transport http web-content-extract-mcp https://web-content-extract-mcp.mcpize.run/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of Web Content Extract Mcp publish no list of tools, so we do not compare tools.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: Fetch (Reference) · What it can do: Web Content Extract Mcp · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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.