Hydrafetch vs One MCP, many parsers
Hydrafetch is an MCP server published by hydrafetch.com. Marketplaces we read that list it: 1 (Official MCP Registry). 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-17. 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 |  Hydrafetch |  One MCP, many parsers |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.0 No figure published Not marked · First seen |
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
| Fact | Hydrafetch | One MCP, many parsers |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | No figure on GitHub | 0 |
| Forks (GitHub) (differs) | No figure on GitHub | 1 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (api.hydrafetch.com/mcp) | On your machine (https://github.com/adelaidasofia/parse-mcp/releases/download/v0.1.0/parse-mcp.mcpb) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 1 |
| Hooks it runs (differs) | Not published | 1 |
| Parts of the bundle (differs) | Not a bundle | 2 |
| Licence | Not stated | Not stated |
| Repository (differs) | Not stated | github.com/adelaidasofia/parse-mcp |
| Changes in the last 7 days (differs) | 0 | 4 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 40 h ago, requires a key | no remote endpoint we check |
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
Hydrafetch
Turn any URL into clean Markdown and structured data. Scrape, crawl, search and extract.
One MCP, many parsers
One MCP, many parsers. Routes between markitdown, Docling, and LlamaParse. Plus an interpret tool…
How to run each
Hydrafetch As a remote MCP server
claude mcp add --transport http web https://api.hydrafetch.com/mcpOne MCP, many parsers As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install parse-mcp@claude-communityRequires: LLAMAPARSE_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Hydrafetch has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of Hydrafetch publish no settings it asks for, so we do not compare settings.
What it can do: Hydrafetch · What it can do: One MCP, many parsers · Compare two other plugins
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.