Skip to main content

email-check

ai.kaiv/email-checkVersion 1.0.0

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

Status

Responds194 msAnswered our handshake without sign-in.

Registry data may be out of date

We could not refresh it, so this page shows the last copy.
Last checked
Nov 14, 2026, 13:33 UTC
Latency
194 ms
Remotes responding
1 of 1
Sign-in
No sign-in
Hosting
Hosted outside the EU (detected)
Registry data as of
Nov 14, 2026, 22:14 UTC

Data from the official MCP Registry, checked by run.zero. How we check

Connect

Streamable HTTP
https://api.kaiv.ai/api/bridge/mcp/email-check-b6ab5250Responds194 ms
No sign-in

Claude Code

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

Claude Desktop and claude.ai

Settings > Connectors > Add custom connector
Name: email-check
Remote MCP server URL: https://api.kaiv.ai/api/bridge/mcp/email-check-b6ab5250

Cursor

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

VS Code

code --add-mcp '{"name":"email-check","type":"http","url":"https://api.kaiv.ai/api/bridge/mcp/email-check-b6ab5250"}'

Built your own server? run.zero hosts MCP servers on European infrastructure.

Host your own MCP server on run.zero

Tools

4 tools

Tools of email-check
Read-only
Idempotent
Open world
check_email_domainFull 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.NoYesYesYes
get_dmarc_recordDMARC 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.NoYesYesYes
get_mx_recordsMail 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.NoYesYesYes
get_spf_recordSPF 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.NoYesYesYes

Details

Registry status
Active
Published
Aug 21, 2026
Updated
Aug 21, 2026
Website
Not given
Repository
Not given
Categories (suggested)
CommunicationSecuritySuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
GDPR
Not declared

Are you the operator? Claim this listing