Email Check MCP Server

by kaiv Your server? Claim it

answering

Email Check is answering right now. Last checked 9 min ago. It exposes 4 tools.

Email posture for any domain: can it receive mail, can it be spoofed? MX, SPF and DMARC.

Uptime history 11 days of history · worst day 99%

11 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

195 ms

Response time

average over 24h

open, no key

Access

streamable-http

Email Check does not always answer

Over the last week it answered 99.8% 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 9 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add email-check --transport http https://api.kaiv.ai/api/bridge/mcp/email-check-b6ab5250

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

{
  "mcpServers": {
    "email-check": {
      "url": "https://api.kaiv.ai/api/bridge/mcp/email-check-b6ab5250"
    }
  }
}

~/.codex/config.toml

[mcp_servers.email-check]
url = "https://api.kaiv.ai/api/bridge/mcp/email-check-b6ab5250"

.cursor/mcp.json

{
  "mcpServers": {
    "email-check": {
      "url": "https://api.kaiv.ai/api/bridge/mcp/email-check-b6ab5250"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "email-check": {
      "url": "https://api.kaiv.ai/api/bridge/mcp/email-check-b6ab5250"
    }
  }
}

Available tools 4

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

dmarc

get_dmarc_record

DMARC record, policy, and whether it actually protects. Returns the DMARC TXT record at _dmarc.<domain>, its policy (none / quarantine / reject), the percentage it applies to, and whether that policy protects against spoofing. Also flags the case of MULTIPLE DMARC records, which RFC 7489 requires receivers to treat as no policy at all — a domain in that state is unprotected however strict its records look. A policy of "none" is monitoring only and does not stop forged mail. Use when assessing whether mail claiming to be from a domain can be trusted.

check_email_domain

Full email posture for a domain: can it receive mail, and can it be spoofed? Runs MX, SPF and DMARC lookups together and returns a plain-language verdict alongside the raw records: can_receive_mail, spoofable, and a list of specific findings. Use this as the default check before emailing an unfamiliar domain, when judging whether inbound mail claiming to be from a domain could be forged, or when auditing your own domains. Prefer this over the single-record tools unless you already know which record you need.

records

get_mx_records

Mail exchanger records for a domain. Returns the MX hosts in priority order and whether any exist. A domain with no MX records cannot receive mail, so sending to it will bounce. Use when you only need deliverability and not spoofing posture; use check_email_domain for the full picture.

spf

get_spf_record

SPF record and how strict it is. Returns the SPF TXT record, the qualifier on its `all` mechanism (fail / softfail / neutral / pass) and what that means in practice, plus whether more than one SPF record exists — which receivers treat as an error, leaving the domain unprotected. Use when diagnosing why mail from a domain is being rejected or marked.

Endpoints

URL	Transport	State	Latency	Checked
https://api.kaiv.ai/api/bridge/mcp/email-check-b6ab5250	streamable-http	answering	370 ms	9 min ago

Alternatives to Email Check

same job, measured the same way

Deliverability Doctor

by integrity-os

Check if a domain can be email-spoofed: SPF, DMARC, DKIM, MX graded from public DNS. Authless.

2 tools answering

fixture.email — Email Testing for Agents

by fixture

Disposable test mailboxes on a real domain: send, receive and assert on real email.

answering

MAILTYPE — Email Domain Capability Intelligence

by gsterlingpress

Email-domain intelligence: MX capability, provider, disposable status, SPF, DMARC, and MTA-STS.

answering

scan.mx Email Diagnostics

by scan

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

6 tools answering

Email Deliverability

by inboxguard

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

28 tools answering

Palisade

by palisade

Monitor and manage email authentication (SPF, DKIM, DMARC, MTA-STS, BIMI) for your domains.

47 installs/wk answering

Clawaimail

by joansongjr

Email infrastructure for AI agents. Create inboxes, send/receive email, and search messages.

53 installs/wk local only

Mail7 Email Validation

by mail7

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

74 installs/wk local only

Email Check — questions

Answers built from our own checks of this server.

What can Email Check do?

It exposes 4 tools, read directly from the server on our last check. Among them: check_email_domain, get_dmarc_record, get_mx_records, get_spf_record. 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 Check 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 195 ms. The bar chart above shows every period we have measured.

How do I connect Email Check?

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 Check need an API key?

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

How fast is Email Check?

It answers our handshake in 195 ms on average, which is faster than 73% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.