Ext Ops Panel
Open dashboard
Comparison

Scrapezy vs One MCP, many parsers

Scrapezy is an MCP server published by Scrapezy. Marketplaces we read that list it: 1 (Docker MCP Catalog). One MCP, many parsers is an MCP server published by adelaidasofia. Marketplaces we read that list it: 2 (Official MCP Registry, Claude Code: claude-plugins-community). As of our marketplace pass on 2026-10-16. 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
MarketplaceScrapezyOne MCP, many parsers
Docker MCP Catalog Listed
Version: sha256:7a19e9b36500
Forks (GitHub): 7
Pulls (Docker Hub): 40 887
Stars (Docker Hub): 3
Stars (GitHub): 14
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.0
Forks (GitHub): 1
Stars (GitHub): 0
Not marked · First seen
Claude Code: claude-plugins-community Not listed Listed
Version: 0.1.0
Forks (GitHub): 1
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

Scrapezy vs One MCP, many parsers
FactScrapezyOne MCP, many parsers
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)14 (better)0 (worse)
Pulls (Docker Hub) (differs)40 887No figure on Docker Hub
Forks (GitHub) (differs)7 (better)1 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/scrapezy)On your machine (https://github.com/adelaidasofia/parse-mcp/releases/download/v0.1.0/parse-mcp.mcpb)
Transportstdiostdio
Tools it declares (differs)1Not published
Environment variables it asks for1, secrets among them: 11, secrets among them: 1
Hooks it runs (differs)Not published1
Parts of the bundle (differs)Not a bundle2
Licence (differs)MITNot stated
Repository (differs)github.com/scrapezy/mcpgithub.com/adelaidasofia/parse-mcp
Changes in the last 7 days (differs)04
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.

One MCP, many parsers

In its own words, on Official MCP Registry:

One MCP, many parsers. Routes between markitdown, Docling, and LlamaParse. Plus an interpret tool…

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)

One MCP, many parsers As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install parse-mcp@claude-community

Requires: LLAMAPARSE_API_KEY (secret)

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

Tools each declares

The marketplaces of One MCP, many parsers publish no list of tools, so we do not compare tools.

Settings each asks for

Only Scrapezy asks for

  • SCRAPEZY_API_KEY (secret)

Only One MCP, many parsers asks for

  • LLAMAPARSE_API_KEY (secret)

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: Scrapezy · What it can do: One MCP, many parsers · 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. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from public marketplace files in GitHub repositories of their authors. 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