Scrapezy vs ScrapeMole Reader
Scrapezy is an MCP server published by Scrapezy. Marketplaces we read that list it: 1 (Docker MCP Catalog). ScrapeMole Reader is an MCP server published by scrapemole.pages.dev. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-13. 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 |  Scrapezy | |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:7a19e9b36500 Forks (GitHub): 7 Pulls (Docker Hub): 40 837 Stars (Docker Hub): 3 Stars (GitHub): 14 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.1.0 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
| Fact | Scrapezy | ScrapeMole Reader |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 14 | No figure on GitHub |
| Pulls (Docker Hub) (differs) | 40 837 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 7 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/scrapezy) | Remote server (reader.scrapemole.workers.dev/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 1 | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | Not published |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/scrapezy/mcp | Not stated |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen (differs) | 2026-10-11 | 2026-10-12 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 3 h ago |
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
A Model Context Protocol server for Scrapezy that enables AI models to extract structured data from websites.
ScrapeMole Reader
Pay-per-call x402 web reading: page to Markdown, link previews, RSS feeds, links, sitemaps.
How to run each
Scrapezy As a local MCP server: Docker image
claude mcp add --env "SCRAPEZY_API_KEY=<YOUR_SCRAPEZY_API_KEY>" --transport stdio scrapezy -- docker run -i --rm -e SCRAPEZY_API_KEY mcp/scrapezyRequires: SCRAPEZY_API_KEY (secret)
ScrapeMole Reader As a remote MCP server
claude mcp add --transport http reader https://reader.scrapemole.workers.dev/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only ScrapeMole Reader has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of ScrapeMole Reader publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of ScrapeMole Reader publish no settings it asks for, so we do not compare settings.
What it can do: Scrapezy · What it can do: ScrapeMole Reader · 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.