email-deliverability-mc
Diagnose email deliverability with read-only checks of DNS, sending IPs, and received message headers.
Check a domain’s email DNS: SPF including the 10-DNS-lookup limit, DMARC policy/reporting, DKIM keys on common or supplied selectors, MX records, ranked problems with fixes, and detected email services.
Check a sending IP: reverse DNS/PTR, whether it resolves back to the IP, and blocklist listings on Spamhaus ZEN, Barracuda, SpamCop, PSBL, Mailspike, and UCEPROTECT level 1, with refused Spamhaus results reported as unknown.
Check email headers: verify SPF, DKIM, DMARC, From alignment, one-click unsubscribe and DKIM coverage, TLS, reverse DNS, and Message-ID against Gmail/Yahoo bulk sender requirements.
Use it via the hosted MCP endpoint or run it locally with npx/Docker; no account or API key is needed.
Detects when a domain uses Amazon SES as its email service provider as part of domain email configuration checks.
Checks received email headers against Gmail's bulk sender requirements, including SPF, DKIM, DMARC alignment, one-click unsubscribe, TLS, reverse DNS, and Message-ID.
Detects when a domain uses Google Workspace as its email service provider as part of domain email configuration checks.
Detects when a domain uses SendGrid as its email service provider as part of domain email configuration checks.
This server has a remotely hosted endpoint. Open its connector listing for connection details, authentication requirements, and setup instructions:
email-deliverability-mcp
An MCP server that lets Claude (or any MCP client) diagnose email deliverability:
check_domain: SPF (including the 10-DNS-lookup limit), DMARC policy and reporting, DKIM keys on common selectors, and MX records, with a ranked list of problems and the fix for each. It also names the email services a domain uses (Google Workspace, SendGrid, Amazon SES and others).check_sending_ip: reverse DNS (PTR) and whether it resolves back to the IP, plus listings on Spamhaus ZEN, Barracuda, SpamCop, PSBL, Mailspike and UCEPROTECT level 1.check_email_headers: paste a received message's headers and check them against Gmail's and Yahoo's sender requirements: SPF, DKIM, DMARC, From alignment, one-click unsubscribe (and whether DKIM covers it), TLS, reverse DNS and Message-ID.
Every tool is read-only: it reads public DNS or the text you give it. Nothing is sent anywhere else, and no account or API key is needed.
Use it without installing
A hosted copy runs at:
https://api.ownmailserver.com/tools/mcpAdd it to Claude as a custom connector (Settings → Connectors → Add custom connector), or in Claude Code:
claude mcp add --transport http email-deliverability https://api.ownmailserver.com/tools/mcpIt's free and needs no account. It's rate-limited per IP, uses public DNS resolvers (so Spamhaus results show as "refused"; see below), and stores nothing. For heavy use or a real Spamhaus answer, run your own copy.
Related MCP server: Domain Deliverability Checker MCP Server
Install
Requires Node.js 20 or later.
Claude Code
claude mcp add email-deliverability -- npx -y email-deliverability-mcpClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"email-deliverability": {
"command": "npx",
"args": ["-y", "email-deliverability-mcp"]
}
}
}Docker
docker build -t email-deliverability-mcp .
docker run -i --rm email-deliverability-mcpThings to ask
"Check example.com's email setup and tell me what to fix first."
"Why might our emails from shop.example be going to spam?" (then paste a message's headers)
"Is 192.0.2.25 on any blocklists? Does its reverse DNS look right?"
"Does this email meet Gmail's bulk sender rules?"
"Our SPF record fails sometimes. Are we over the lookup limit?"
Configuration
Variable | Default | What it does |
| the system resolver | Comma-separated IPs of a recursive resolver you run, used for blocklist lookups. |
| the system resolver | Comma-separated resolver IPs for all other lookups. |
Why BLOCKLIST_DNS matters
Spamhaus refuses queries that arrive through big public resolvers (8.8.8.8, 1.1.1.1 and the like) and answers 127.255.255.x instead. Many blocklist checkers misread that as "listed". This server reports it as refused, meaning unknown, and says so. To get a real Spamhaus answer, point BLOCKLIST_DNS at a recursive resolver of your own, such as unbound on 127.0.0.1.
How the checks work
SPF lookups follow
include:andredirect=recursively and count everyinclude,a,mx,ptr,existsandredirectterm, as RFC 7208 does. More than 10 is a permanent error at most receivers.DKIM keys sit under selectors that only the sender knows, so the server probes about 30 common ones. Pass your own with
dkim_selectors(find it in thes=value of a message'sDKIM-Signatureheader). Domains that answer every name (wildcard DNS) are detected and not reported as having keys.Header checks read the topmost
Authentication-Resultsheader, which is what the recipient's mailbox provider concluded, and the newestReceivedhop that names the sending server.Alignment compares organizational domains with a simple rule (the last two labels, or three for names like
example.co.uk). It's not a full Public Suffix List lookup, so unusual suffixes may be misjudged.
Development
npm install
npm test # unit tests with a fake DNS resolver
npm run build # compiles to dist/
npm run start:http # the HTTP version (PORT, MCP_PATH, TRUST_PROXY, RATE_LIMIT, GLOBAL_LIMIT)About
Built by OwnMailServer, which runs dedicated email sending for businesses that send 250,000 to 1,000,000 emails a month: your own server and IP, a Resend-style API and SMTP, managed warm-up and daily monitoring. OwnMailServer accounts also get a Claude connector for their own sending data: delivery stats, bounces, complaints and message history.
The same checks are available as free web tools: the email health checker and the bulk sender checker.
License
MIT
Available Tools
3 toolscheck_domainCheck a domain's email DNSARead-onlyIdempotentInspect
Check a domain's SPF (including the 10-DNS-lookup limit), DMARC policy and reporting, DKIM keys on common selectors, and MX records. Returns problems ranked by severity with the fix for each, plus the email services the domain uses.
Inputs: domain (required), dkim_selectors.
check_email_headersCheck email headersARead-onlyIdempotentInspect
Check a received email's headers against Gmail's and Yahoo's bulk sender requirements: SPF, DKIM and DMARC results, From domain alignment, one-click unsubscribe (and whether DKIM covers it), TLS, reverse DNS and Message-ID. Use the full headers as the recipient got them (Gmail: Show original).
Inputs: headers (required).
check_sending_ipCheck a sending IPARead-onlyIdempotentInspect
Check a mail server's IP: reverse DNS (PTR) and whether it resolves back to the IP, and listings on Spamhaus ZEN, Barracuda, SpamCop, PSBL, Mailspike and UCEPROTECT level 1. A refused Spamhaus query is reported as unknown, never as a listing.
Inputs: ip (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 3 tools
Each tool takes a fundamentally different input type: a domain, a sending IP, or an email's raw headers. There is no plausible way to confuse check_domain with check_sending_ip or check_email_headers, and the descriptions reinforce the boundary by listing what each inspects.
All three tools use the identical check_<noun> pattern with nouns that accurately describe the target (domain, sending_ip, email_headers). The convention is predictable and would extend cleanly if more checks were added.
Three tools is lean but each maps to a distinct diagnostic axis (domain auth, IP reputation, message-level compliance), so none is filler. It is on the sparse side of the 3-15 range for the breadth of email deliverability, but not thin enough to be a real mismatch.
The surface covers the three core pillars: domain authentication records, IP reputation/blocklists, and header-level bulk-sender compliance, all with actionable severity-ranked fixes. Minor gaps remain, such as BIMI/MTA-STS/TLS-RPT checks, DMARC aggregate report analysis, and batch checking of multiple domains or IP ranges, but agents can work around these.
Maintenance
Related MCP Connectors
Check any domain's email deliverability: MX, SPF, DKIM, DMARC, MTA-STS, TLS-RPT, BIMI, blacklists.
Email deliverability checks: SPF, DKIM, DMARC, BIMI, MTA-STS, blacklists, headers, spam words
Checks any domain's DMARC, SPF, MX and DKIM setup, scores it 0-100, and ranks the fixes.
Check SPF, DKIM, DMARC, MX, MTA-STS, TLS-RPT, BIMI, DANE, DNSSEC and TXT; read headers and bounces.
Related MCP Servers
- AlicenseAqualityDmaintenanceMCP server for email deliverability: validate SPF/DKIM/DMARC/BIMI, check blacklists, test SMTP/IMAP, look up DNS, and generate ready-to-deploy records for any major email provider. Ships with two one-click prompts (audit-deliverability, setup-dns). Public, no auth.17MIT
- AlicenseAqualityBmaintenanceEnables auditing any domain's email deliverability and DNS health, including SPF, DKIM, DMARC, MX, mail provider, DNS blacklist status, catch-all, domain age, and a deliverability score.1126 npm1MIT
- AlicenseNot gradedqualityCmaintenanceAudits email deliverability configuration for a domain, checking SPF, DKIM, DMARC, and MX records, returning a score and recommendations.MIT
- AlicenseAqualityBmaintenanceProvides comprehensive email deliverability and domain registration analysis, evaluating SPF, DKIM, DMARC, DNS records, and expiry to identify issues and suggest fixes.51MIT