webclaw vs Web Page Fetcher
webclaw is an MCP server published by 0xMassi. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). Web Page Fetcher is an MCP server published by paimonchan. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-28. 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 |  Web Page Fetcher | |
|---|---|---|
| Official MCP Registry | Listed Version: 0.6.17 Downloads/month (npm): 611 Downloads/week (npm): 179 Not marked · First seen |
Listed Version: 0.1.2 Forks (GitHub): 0 Stars (GitHub): 3 Not marked · First seen |
| npm registry (MCP servers) | Listed Version: 0.7.0 Downloads/month (npm): 611 Downloads/week (npm): 179 Forks (GitHub): 238 Stars (GitHub): 2 405 Not marked · First seen |
Not listed |
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 | webclaw | Web Page Fetcher |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 2 405 (better) | 3 (worse) |
| Forks (GitHub) (differs) | 238 (better) | 0 (worse) |
| Last release (differs) | 2026-10-20 | Not published |
| Where it runs (differs) | On your machine (@webclaw/mcp) | On your machine (https://github.com/paimonchan/paimon-mcp-fetch/releases/download/v0.1.2/paimon-mcp-fetch-0.1.2-windows-amd64.zip) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 4, secrets among them: 0 |
| Licence (differs) | AGPL-3.0-only | Not stated |
| Repository (differs) | github.com/0xmassi/webclaw | github.com/paimonchan/paimon-mcp-fetch |
| Changes in the last 7 days | 0 | 0 |
| 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
webclaw
Turn any URL into clean markdown/JSON for AI agents. Self-hostable web content extraction.
Web Page Fetcher
Fetch web pages with SSRF protection. Returns clean, readable markdown from any URL.
How to run each
webclaw As a local MCP server: npm package
claude mcp add --transport stdio webclaw -- npx -y @webclaw/mcpWeb Page Fetcher
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
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 webclaw publish no settings it asks for, so we do not compare settings.
What it can do: webclaw · What it can do: Web Page Fetcher · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.