Ext Ops Panel
Open dashboard
Comparison

Scrapezy vs webclaw

Scrapezy is an MCP server published by Scrapezy. Marketplaces we read that list it: 1 (Docker MCP Catalog). webclaw is an MCP server published by 0xMassi. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-12. 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
MarketplaceScrapezywebclaw
Docker MCP Catalog Listed
Version: sha256:7a19e9b36500
Forks (GitHub): 7
Pulls (Docker Hub): 40 825
Stars (Docker Hub): 3
Stars (GitHub): 14
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.6.17
No figure published
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

Scrapezy vs webclaw
FactScrapezywebclaw
Marketplaces that list it11
Stars (GitHub) (differs)14No figure on GitHub
Pulls (Docker Hub) (differs)40 825No figure on Docker Hub
Forks (GitHub) (differs)7No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/scrapezy)On your machine (@webclaw/mcp)
Transportstdiostdio
Tools it declares (differs)1Not published
Environment variables it asks for (differs)1, secrets among them: 1Not published
Licence (differs)MITNot stated
Repository (differs)github.com/scrapezy/mcpNot stated
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

Scrapezy

In its own words, on Docker MCP Catalog:

A Model Context Protocol server for Scrapezy that enables AI models to extract structured data from websites.

webclaw

In its own words, on Official MCP Registry:

Turn any URL into clean markdown/JSON for AI agents. Self-hostable web content extraction.

How to run each

Scrapezy As a local MCP server: Docker image

Claude Code
claude mcp add --env "SCRAPEZY_API_KEY=<YOUR_SCRAPEZY_API_KEY>" --transport stdio scrapezy -- docker run -i --rm -e SCRAPEZY_API_KEY mcp/scrapezy

Requires: SCRAPEZY_API_KEY (secret)

webclaw As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio webclaw -- npx -y @webclaw/mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

The marketplaces of webclaw publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of webclaw publish no settings it asks for, so we do not compare settings.

What it can do: Scrapezy · What it can do: webclaw · 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.

Where the data comes from: how the catalog is built