ai.kaiv/email-check

Official4 tools

by kaiv

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

Model Context Protocol (MCP) Server: ai.kaiv/email-check

The ai.kaiv/email-check MCP server provides an “Email posture for any domain” assessment focused on whether a domain can receive mail and whether it can be spoofed. The description specifies checks for MX, SPF, and DMARC to evaluate email configuration and related risks.

🛠️ Key Features

Email posture analysis for any domain
Verifies mail receiving capability
Assesses spoofing risk using MX, SPF, and DMARC
Exposes 4 tools (toolCount: 4)

🚀 Use Cases

Determine whether a domain can receive email
Evaluate domain email authentication posture
Check spoofing susceptibility via MX/SPF/DMARC

⚡ Developer Benefits

Structured analysis based on MX, SPF, and DMARC for automation

⚠️ Limitations

Scope is limited to email posture and spoofing related to MX, SPF, and DMARC

Captured live from the server via tools/list.

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.

Parameters1

domain

string

required

Domain to check, e.g. "example.com". A full email address is accepted and the domain is taken from it.

Raw schema

{
  "type": "object",
  "properties": {
    "domain": {
      "type": "string",
      "x-in": "query",
      "example": "kaiv.ai",
      "description": "Domain to check, e.g. \"example.com\". A full email address is accepted and the domain is taken from it."
    }
  },
  "required": [
    "domain"
  ]
}

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.

Parameters1

domain

string

required

Domain to check, e.g. "example.com". A full email address is accepted and the domain is taken from it.

Raw schema

{
  "type": "object",
  "properties": {
    "domain": {
      "type": "string",
      "x-in": "query",
      "example": "kaiv.ai",
      "description": "Domain to check, e.g. \"example.com\". A full email address is accepted and the domain is taken from it."
    }
  },
  "required": [
    "domain"
  ]
}

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.

Parameters1

domain

string

required

Domain to check, e.g. "example.com". A full email address is accepted and the domain is taken from it.

Raw schema

{
  "type": "object",
  "properties": {
    "domain": {
      "type": "string",
      "x-in": "query",
      "example": "kaiv.ai",
      "description": "Domain to check, e.g. \"example.com\". A full email address is accepted and the domain is taken from it."
    }
  },
  "required": [
    "domain"
  ]
}

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.

Parameters1

domain

string

required

Domain to check, e.g. "example.com". A full email address is accepted and the domain is taken from it.

Raw schema

{
  "type": "object",
  "properties": {
    "domain": {
      "type": "string",
      "x-in": "query",
      "example": "kaiv.ai",
      "description": "Domain to check, e.g. \"example.com\". A full email address is accepted and the domain is taken from it."
    }
  },
  "required": [
    "domain"
  ]
}

Install

Tools (4)

check_email_domainget_dmarc_recordget_mx_recordsget_spf_record

Remote endpoint

Streamable HTTP

Hosted server - connect over the network, no local install.

url

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

Add to VS Code Add to Cursor

claude_desktop_config.json

json

{
  "mcpServers": {
    "email-check": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://api.kaiv.ai/api/bridge/mcp/email-check-b6ab5250"
      ]
    }
  }
}

Desktop config is stdio-only; this bridges via mcp-remote. Native remote: Settings > Connectors.

Model Context Protocol (MCP) Server: ai.kaiv/email-check

🛠️ Key Features

🚀 Use Cases

⚡ Developer Benefits

⚠️ Limitations

check_email_domain

get_dmarc_record

get_mx_records

get_spf_record

Install

Remote endpoint

Related servers