Email Deliverability Audit API MCP Server

by br0ski777 Your server? Claim it

not responding

Email Deliverability Audit API is listed as active in the registry but did not answer our last check. It exposes 1 tools. Last commit 2 Sep 2026.

Audit email domain deliverability: SPF, DKIM, DMARC, MX. Score 0-100. x402.

Uptime history 51 days of history · worst day 0%

51 days agonow

0.0%

Uptime 24h

0 of 91 checks

Tools

read from the server

174 ms

Response time

average over 24h

Stars

last commit 2 Sep 2026

What changed 3652

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 8 August 2026. No other catalogue keeps this.

17 Sep a tool description was rewritten71 times that day email_audit_deliverability

16 Sep a tool description was rewritten92 times that day email_audit_deliverability

15 Sep a tool description was rewritten91 times that day email_audit_deliverability

14 Sep a tool description was rewritten91 times that day email_audit_deliverability

13 Sep a tool description was rewritten92 times that day email_audit_deliverability

12 Sep a tool description was rewritten91 times that day email_audit_deliverability

11 Sep a tool description was rewritten90 times that day email_audit_deliverability

10 Sep a tool description was rewritten93 times that day email_audit_deliverability

9 Sep a tool description was rewritten91 times that day email_audit_deliverability

8 Sep a tool description was rewritten91 times that day email_audit_deliverability

and 3642 more, back to 8 August 2026

Email Deliverability Audit API does not always answer

Over the last week it answered 30.0% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 3 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add email-deliverability --transport http https://email-deliverability.api.klymax402.com/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "email-deliverability": {
      "url": "https://email-deliverability.api.klymax402.com/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.email-deliverability]
url = "https://email-deliverability.api.klymax402.com/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "email-deliverability": {
      "url": "https://email-deliverability.api.klymax402.com/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "email-deliverability": {
      "url": "https://email-deliverability.api.klymax402.com/mcp"
    }
  }
}

Available tools 1

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

email_audit_deliverability

Use this when you need to audit email deliverability configuration for a domain. Returns structured JSON with authentication record analysis and a deliverability score 0-100. POST variant of email_audit_deliverability -- same params passed as JSON body instead of query string. 1. score (number 0-100) -- overall deliverability health score 2. spf (object) -- SPF record found, valid syntax, includes count, too-many-lookups flag 3. dkim (object) -- DKIM selectors tested (google, default, selector1, selector2), which ones pass 4. dmarc (object) -- DMARC record found, policy (none/quarantine/reject), rua/ruf reporting addresses 5. mx (object) -- MX records found, priorities, mail server hostnames 6. recommendations (array) -- prioritized list of fixes to improve inbox placement Example output: {"score":65,"spf":{"found":true,"valid":true,"record":"v=spf1 include:_spf.google.com ~all"},"dkim":{"google":true,"default":false},"dmarc":{"found":true,"policy":"none","record":"v=DMARC1; p=none"},"mx":[{"priority":10,"exchange":"alt1.gmail-smtp-in.l.google.com"}],"recommendations":["Upgrade DMARC policy from none to quarantine","Add DKIM for default selector"]} Use this BEFORE launching email campaigns, onboarding new domains for outreach, or diagnosing inbox placement issues. Essential for email marketers, sales teams, and IT admins managing domain reputation. Do NOT use for single email validation -- use email_verify_address instead. Do NOT use for finding email addresses -- use email_find_by_name instead. Do NOT use for domain WHOIS/DNS -- use domain_lookup_intelligence instead.

Endpoints

URL	Transport	State	Latency	Checked
https://email-deliverability.api.klymax402.com/mcp	sse	answering	174 ms	3 min ago

Alternatives to Email Deliverability Audit API

same job, measured the same way

MCP Domain Deliverability Checker

by mambabuilt

Audit a domain email deliverability via Apify: SPF, DKIM, DMARC, MX, blacklist, catch-all, age.

38 installs/wk local only

Email Deliverability

by inboxguard

Scan and fix a domain's email deliverability (SPF, DKIM, DMARC, MTA-STS, BIMI, DNS blocklists).

28 tools answering

scan.mx Email Diagnostics

by scan

Check email deliverability for a domain: MX, SPF, DKIM, DMARC, blacklists. Graded, no key.

6 tools answering

Domain Security

by ortamarco

Audit a domain's email and web security: SPF, DKIM, DMARC, MTA-STS, DNSSEC, TLS, WHOIS. No API keys.

247 installs/wk local only

Mail7 Email Validation

by mail7

Verify email addresses, clean lists, and audit a domain SPF, DKIM, DMARC and MX setup.

35 installs/wk local only

MailX Email Deliverability

by themailx

Check SPF/DKIM/DMARC/BIMI, blacklists, SMTP/IMAP; DNS lookups; generate email DNS records.

16 tools answering

Inbox Check — Email Deliverability Test

by live-direct-marketing

Email inbox placement tests across Gmail, Outlook, Yahoo, Mail.ru, Yandex (SPF/DKIM/DMARC).

34 installs/wk local only

Domainposture

by domainposture

Remote MCP server: 19 domain-hygiene and email-auth tools (DNS, SPF, DMARC, DKIM, TLS).

22 tools answering

Email Deliverability Audit API — questions

Answers built from our own checks of this server.

What can Email Deliverability Audit API do?

It exposes 1 tools, read directly from the server on our last check. Among them: email_audit_deliverability. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Email Deliverability Audit API working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 0 of 91 checks got a reply (0.0%), average response time 174 ms. The bar chart above shows every period we have measured.

The registry lists Email Deliverability Audit API as active — why does it not respond?

The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.

How do I connect Email Deliverability Audit API?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Email Deliverability Audit API need an API key?

No. Email Deliverability Audit API completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 1 of them are readable on this page. This is what we observed, not what the docs claim.

Is Email Deliverability Audit API open source?

Yes — it is published under the MIT licence, written in TypeScript and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.