mcpbeat

scan.mx Email Diagnostics MCP Server

mx.scan/diagnostics
answering

scan.mx Email Diagnostics is answering right now. Last checked 7 min ago. It exposes 6 tools.

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

Uptime history 40 hours of history
40 hours agonow
100.0%
Uptime 24h
91 of 91 checks
6
Tools
read from the server
187 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

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

run in your terminal
claude mcp add diagnostics --transport http https://api.scan.mx/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "diagnostics": {
      "url": "https://api.scan.mx/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.diagnostics]
url = "https://api.scan.mx/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "diagnostics": {
      "url": "https://api.scan.mx/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "diagnostics": {
      "url": "https://api.scan.mx/mcp"
    }
  }
}

Available tools 6

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

blacklist
check_blacklist
Check whether the domain and its mail server IPs are listed on the Spamhaus (ZEN, DBL, ZRD, AuthBL), SpamCop, GBUdb and PSBL blocklists.
check
check_mx
Check the MX records of a domain: presence, hostnames, resolution, null-MX, and common misconfigurations.
dkim
check_dkim
Check DKIM signing keys for a domain. Without a selector, common provider selectors are probed. Pass an explicit selector to look up that exact key at selector._domainkey.
dmarc
check_dmarc
Check the domain DMARC policy at _dmarc: presence, policy strength (none/quarantine/reject), and reporting.
domain
check_domain
Run the full email and DNS deliverability check for a domain: MX, SPF, DKIM, DMARC, DNS health, provider detection, and blacklists. Returns a letter grade (A to F), a 0 to 100 score, and every individual check with its RFC reference. Set include_smtp to also run a live SMTP probe of the mail servers: the probe is non-blocking, so when smtp_status is "pending" or "running" call this tool again (poll_after_seconds hints how long to wait) until smtp_status is "complete" and the SMTP checks appear in checks.
spf
check_spf
Check the domain SPF policy: presence, syntax, the all qualifier, and the 10-lookup limit.

Endpoints

URLTransportStateLatencyChecked
https://api.scan.mx/mcp streamable-http answering 260 ms 7 min ago

scan.mx Email Diagnostics — questions

Answers built from our own checks of this server.

What can scan.mx Email Diagnostics do?
It exposes 6 tools, read directly from the server on our last check. Among them: check_blacklist, check_dkim, check_dmarc, check_domain, check_mx, check_spf. 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 scan.mx Email Diagnostics working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 187 ms. The bar chart above shows every period we have measured.
How do I connect scan.mx Email Diagnostics?
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 scan.mx Email Diagnostics need an API key?
No. scan.mx Email Diagnostics completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 6 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is scan.mx Email Diagnostics?
It answers our handshake in 187 ms on average, which is faster than 65% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.