Scrapezy vs com.scrapeunblocker/scrapeunblocker-mcp-remote
Scrapezy is an MCP server published by Scrapezy. Marketplaces we read that list it: 1 (Docker MCP Catalog). com.scrapeunblocker/scrapeunblocker-mcp-remote is an MCP server published by scrapeunblocker.com. 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 |  Scrapezy |  com.scrapeunblocker/scrapeunblocker-mcp-remote |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:7a19e9b36500 Forks (GitHub): 8 Pulls (Docker Hub): 41 252 Stars (Docker Hub): 3 Stars (GitHub): 14 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.9.1 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 | Scrapezy | com.scrapeunblocker/scrapeunblocker-mcp-remote |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 14 (better) | 0 (worse) |
| Pulls (Docker Hub) (differs) | 41 252 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 8 (better) | 0 (worse) |
| Last release (differs) | Not published | 2026-10-25 |
| Where it runs (differs) | On your machine (mcp/scrapezy) | Remote server (mcp.scrapeunblocker.com/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 | github.com/scrapeunblocker/scrapeunblocker-mcp-remote |
| Changes in the last 7 days (differs) | 0 | 3 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 5 days ago, requires a key |
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.
com.scrapeunblocker/scrapeunblocker-mcp-remote
Fetch any page's HTML or AI-parsed JSON, Google results, or 100+ site plugins via ScrapeUnblocker
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)
com.scrapeunblocker/scrapeunblocker-mcp-remote As a remote MCP server
claude mcp add --transport http scrapeunblocker-mcp-remote https://mcp.scrapeunblocker.com/mcp --header "x-scrapeunblocker-key: <YOUR_X_SCRAPEUNBLOCKER_KEY>"Requires: x-scrapeunblocker-key header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only com.scrapeunblocker/scrapeunblocker-mcp-remote has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of com.scrapeunblocker/scrapeunblocker-mcp-remote publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of com.scrapeunblocker/scrapeunblocker-mcp-remote publish no settings it asks for, so we do not compare settings.
What it can do: Scrapezy · What it can do: com.scrapeunblocker/scrapeunblocker-mcp-remote · 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.