All servers · Email & messaging · Cloud & networking

ai.kaiv/email-check

ai.kaiv/email-check · v1.0.0

Measured by MCP Station

Last check	Reachable
Checked at	—
Check success 7 / 30 days	—
First-try success 30 days	—
Median response	—
Lookups 30 days	—
Authentication	No auth
MCP version	2025-06-18
Rank score	—
Declared risk	Read-only (all tools declare readOnlyHint)
Capabilities declared	tools
Tool definitions	4 tools · with description 100% · input schema is an object 100% · read/destructive hints 100%

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

streamable-http · https://api.kaiv.ai/api/bridge/mcp/email-check-b6ab5250

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

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

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 unfamili
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 re
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.
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

JSON · Text for agents · Registry updated 2026-08-21