Scrapezy vs upAPI
Scrapezy is an MCP server published by Scrapezy. Marketplaces we read that list it: 1 (Docker MCP Catalog). upAPI is an MCP server published by DevinoSolutions. 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 |  Scrapezy |  upAPI |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:7a19e9b36500 Forks (GitHub): 7 Pulls (Docker Hub): 40 870 Stars (Docker Hub): 3 Stars (GitHub): 14 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.2.0 Downloads/month (npm): 1 088 Downloads/week (npm): 254 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 | upAPI |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 14 (better) | 0 (worse) |
| Pulls (Docker Hub) (differs) | 40 870 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 7 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/scrapezy) | Remote server (app.upapi.io/api/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 1 | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | 2, secrets among them: 1 |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/scrapezy/mcp | github.com/devinosolutions/upapi-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 | Responded 19 h 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.
upAPI
All public upAPI operations as MCP tools: web scraping, search, screenshots, PDF, OCR and more.
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)
upAPI As a remote MCP server
claude mcp add --transport http upapi-mcp https://app.upapi.io/api/mcpRequires: UPAPI_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only upAPI has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of upAPI publish no list of tools, so we do not compare tools.
Settings each asks for
Only Scrapezy asks for
SCRAPEZY_API_KEY (secret)
Only upAPI asks for
UPAPI_API_KEY (secret)UPAPI_TOOL_MODE
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Scrapezy · What it can do: upAPI · 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.