defluff vs MailProbe
defluff is a plugin bundle for AI coding tools published by FinAegis. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). MailProbe is an MCP server published by mailprobe.dev. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-10-22. 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 |  defluff |  MailProbe |
|---|---|---|
| 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.1.1 Downloads/month (npm): 707 Downloads/week (npm): 668 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 1.1.1 Downloads/month (npm): 707 Downloads/week (npm): 668 Forks (GitHub): 0 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 | defluff | MailProbe |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) | 0 | 0 |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server or your machine |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 1 |
| Parts of the bundle (differs) | 1 | Not a bundle |
| Licence | MIT | MIT |
| Repository (differs) | github.com/finaegis/defluff | github.com/jamalofski/mailprobe-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 2 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
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.
MailProbe
Verify email addresses in real time: deliverability, disposable and role addresses, typo fixes.
How to run each
defluff As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install defluff@claude-communityMailProbe As a remote MCP server
claude mcp add --transport http mailprobe https://mailprobe.dev/mcp --header "Authorization: Bearer <YOUR_API_KEY>"Requires: MAILPROBE_API_KEY (secret), Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only MailProbe 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 defluff publish no settings it asks for, so we do not compare settings.
What it can do: defluff · What it can do: MailProbe · 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. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.