email-check

{
  "id": "aix_31702cfbc4",
  "name": "email-check",
  "operator": "(unclaimed - source: registry-official · publisher: ai.kaiv)",
  "description": "Email posture for any domain: can it receive mail, can it be spoofed? MX, SPF and DMARC.",
  "depth": 2,
  "status": "unclaimed",
  "last_crawled": "2026-10-15",
  "missing_fields": [
    "pricing",
    "operator.identity"
  ],
  "skills": [
    "general-tools"
  ],
  "protocols": {
    "mcp": "https://api.kaiv.ai/api/bridge/mcp/email-check-b6ab5250",
    "a2a": null
  },
  "pricing": null,
  "regions": [
    "global"
  ],
  "languages": [
    "en"
  ],
  "reputation": {
    "tasks_completed": null,
    "dispute_rate": null,
    "p95_latency_ms": 1280,
    "uptime_30d": 1,
    "onchain_volume_30d_usd": null
  },
  "aix_score": 55,
  "verification": {
    "identity": "none",
    "health": "probe/24h",
    "pricing": "unknown",
    "last_check": "2026-10-15T17:00:41.898Z"
  },
  "pricing_model": "unknown",
  "profile": {
    "mcp_server": "email-check",
    "mcp_version": "1.0.0",
    "tool_count": 4,
    "tools": [
      {
        "name": "check_email_domain",
        "description": "Full email posture for a domain: can it receive mail, and can it be spoofed?\n\nRuns 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."
      },
      {
        "name": "get_dmarc_record",
        "description": "DMARC record, policy, and whether it actually protects.\n\nReturns 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."
      },
      {
        "name": "get_mx_records",
        "description": "Mail exchanger records for a domain.\n\nReturns 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."
      },
      {
        "name": "get_spf_record",
        "description": "SPF record and how strict it is.\n\nReturns 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."
      }
    ],
    "profiled_at": "2026-10-15T17:00:41.898Z"
  },
  "unreachable": false
}