Ext Ops Panel
Open dashboard
Comparison

defluff vs io.github.ryuamarines/email-extractor

defluff is a plugin bundle for AI coding tools published by FinAegis. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). io.github.ryuamarines/email-extractor is an MCP server published by ryuamarines. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-24. 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
Marketplacedefluffio.github.ryuamarines/email-extractor
Claude Code: claude-plugins-community Listed
Version: 544c39e
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.0
No figure published
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

defluff vs io.github.ryuamarines/email-extractor
Factdefluffio.github.ryuamarines/email-extractor
Marketplaces that list it11
Stars (GitHub) (differs)0No figure on GitHub
Forks (GitHub) (differs)0No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (faceted-napped-debtless.ngrok-free.dev/email-extractor/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)1Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/finaegis/defluffNot stated
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkAnswered with HTTP 404 (5 days ago)

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

defluff

In its own words, on Claude Code: claude-plugins-community:

Reverse the AI in corporate email. For every message Defluff guesses what prompt the sender gave an LLM, classifies urgency (ACTIONABLE / RESPONSE-NEEDED / FYI / NOISE), and extracts 3–5 bullets of real intent. Handles single emails, threads, and batch triage. Detects invoice fraud / BEC, phishing, fake recruiters, fake interviews, conference scams, and crypto pitches with specifically named red flags — lookalike domains, fake forwarded approvals, urgency + payment redirects.

io.github.ryuamarines/email-extractor

In its own words, on Official MCP Registry:

Extracts emails from texts. x402 payment required (testnet USDC).

How to run each

defluff As a Claude Code plugin

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

io.github.ryuamarines/email-extractor As a remote MCP server

Claude Code
claude mcp add --transport http email-extractor https://faceted-napped-debtless.ngrok-free.dev/email-extractor/mcp

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

Only io.github.ryuamarines/email-extractor 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

Neither one's marketplaces publish the settings it asks for.

What it can do: defluff · What it can do: io.github.ryuamarines/email-extractor · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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.

Where the data comes from: how the catalog is built