Ext Ops Panel
Open dashboard
Comparison

dead-letter vs One MCP, many parsers

dead-letter is an MCP server published by BigCactusLabs. 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
Marketplacedead-letterOne MCP, many parsers
Official MCP Registry Listed
Version: 0.4.10
Downloads/month (PyPI): 1 305
Downloads/week (PyPI): 153
Forks (GitHub): 0
Stars (GitHub): 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

dead-letter vs One MCP, many parsers
Factdead-letterOne MCP, many parsers
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)8 (better)0 (worse)
Forks (GitHub) (differs)0 (worse)1 (better)
Last release (differs)2026-10-29Not published
Where it runs (differs)On your machine (dead-letter)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)Not published1, secrets among them: 1
Hooks it runs (differs)Not published1
Parts of the bundle (differs)Not a bundle2
LicenceNot statedNot stated
Repository (differs)github.com/bigcactuslabs/dead-lettergithub.com/adelaidasofia/parse-mcp
Changes in the last 7 days (differs)20
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

dead-letter

In its own words, on Official MCP Registry:

Convert .eml and .mbox email to clean Markdown for RAG, LLM pipelines, and local knowledge bases

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

dead-letter As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio dead-letter -- uvx --python 3.12 --from "dead-letter[mcp]==0.4.10" dead-letter dead-letter-mcp

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

The marketplaces of dead-letter publish no settings it asks for, so we do not compare settings.

What it can do: dead-letter · 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