Skip to main content
Glama
email-deliverability-mc

email-deliverability-mc

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/mcp

Add 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/mcp

It'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-mcp

Claude 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-mcp

Things 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

BLOCKLIST_DNS

the system resolver

Comma-separated IPs of a recursive resolver you run, used for blocklist lookups.

DNS_SERVERS

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: and redirect= recursively and count every include, a, mx, ptr, exists and redirect term, 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 the s= value of a message's DKIM-Signature header). Domains that answer every name (wildcard DNS) are detected and not reported as having keys.

  • Header checks read the topmost Authentication-Results header, which is what the recipient's mailbox provider concluded, and the newest Received hop 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 tools
check_domainCheck a domain's email DNSA
Read-onlyIdempotent
Inspect

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 headersA
Read-onlyIdempotent
Inspect

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 IPA
Read-onlyIdempotent
Inspect

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

    A4.2/5.0

    Scored across 3 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count4/5

    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.

    Completeness4/5

    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

    ActivityMaintained
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      D
      maintenance
      MCP 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.
      17
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Audits email deliverability configuration for a domain, checking SPF, DKIM, DMARC, and MX records, returning a score and recommendations.
      MIT