io.inboxguard/email-deliverability vs scan.mx Email Diagnostics
io.inboxguard/email-deliverability is an MCP server published by inboxguard.io. Marketplaces we read that list it: 1 (Official MCP Registry). scan.mx Email Diagnostics is an MCP server published by scan.mx. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-14. 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 |  io.inboxguard/email-deliverability |  scan.mx Email Diagnostics |
|---|---|---|
| Official MCP Registry | Listed Version: 1.2.0 No figure published Not marked · First seen |
Listed Version: 1.1.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
| Fact | io.inboxguard/email-deliverability | scan.mx Email Diagnostics |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Last release (differs) | Not published | 2026-10-13 |
| Where it runs (differs) | Remote server (mcp.inboxguard.io/mcp) | Remote server (api.scan.mx/mcp) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository | Not stated | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 18 h ago | Responded 13 h 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
io.inboxguard/email-deliverability
Scan and fix a domain's email deliverability (SPF, DKIM, DMARC, MTA-STS, BIMI, DNS blocklists).
scan.mx Email Diagnostics
Email deliverability check: MX, SPF, DKIM, DMARC, blacklists, MTA-STS, DNSSEC, BIMI. Graded, no key.
How to run each
io.inboxguard/email-deliverability As a remote MCP server
claude mcp add --transport http email-deliverability https://mcp.inboxguard.io/mcpscan.mx Email Diagnostics As a remote MCP server
claude mcp add --transport http diagnostics https://api.scan.mx/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Both endpoints responded at the last daily check. How we check endpoints
Tools each declares
Neither the marketplaces of io.inboxguard/email-deliverability nor its endpoint list any tools, so we do not compare tools.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: io.inboxguard/email-deliverability · What it can do: scan.mx Email Diagnostics · Compare two other plugins
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.