Ext Ops Panel
Open dashboard
Comparison

com.wrapper-agency.parsedoc/parser vs One MCP, many parsers

com.wrapper-agency.parsedoc/parser is an MCP server published by parsedoc.wrapper-agency.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-30. 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
Marketplacecom.wrapper-agency.parsedoc/parserOne MCP, many parsers
Official MCP Registry Listed
Version: 0.1.2
Downloads/month (npm): 105
Downloads/week (npm): 8
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

com.wrapper-agency.parsedoc/parser vs One MCP, many parsers
Factcom.wrapper-agency.parsedoc/parserOne MCP, many parsers
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)No figure on GitHub0
Forks (GitHub) (differs)No figure on GitHub1
Last releaseNot publishedNot published
Where it runs (differs)On your machine (parsedoc-mcp)On your machine (https://github.com/adelaidasofia/parse-mcp/releases/download/v0.1.0/parse-mcp.mcpb)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)2, secrets among them: 11, secrets among them: 1
Hooks it runs (differs)Not published1
Parts of the bundle (differs)Not a bundle2
LicenceNot statedNot stated
Repository (differs)Not statedgithub.com/adelaidasofia/parse-mcp
Changes in the last 7 days00
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

com.wrapper-agency.parsedoc/parser

In its own words, on Official MCP Registry:

Parse receipts & invoices into structured JSON. Pay per call in USDC (x402 on Base), no API key.

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

com.wrapper-agency.parsedoc/parser As a local MCP server: npm package

Claude Code
claude mcp add --env "X402_PRIVATE_KEY=<YOUR_X402_PRIVATE_KEY>" --transport stdio parser -- npx -y parsedoc-mcp

Requires: X402_PRIVATE_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

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Only com.wrapper-agency.parsedoc/parser asks for

  • PARSEDOC_URL
  • X402_PRIVATE_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: com.wrapper-agency.parsedoc/parser · 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.

Where the data comes from: how the catalog is built