email-check

connects

api.kaiv.ai

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

https://api.kaiv.ai/api/bridge/mcp/email-check-b6ab5250No authMCP 2025-06-18v1.0.0last checked 24 Aug 2026spoke MCP on 2 of 2 checks (30 days)initialize in 1219 ms

How to authenticate

Checked against the endpoint by our probe on 24 Aug 2026. These are the capabilities the server advertises, not a prediction about any particular client.

Scheme	No auth
Protected-resource metadata	✕Not found Without it a client has to guess where the authorization server lives.
Anonymous access	Handshake succeeds; 4 tools listable

What the probe found

No CORS headers for browser-based clients

A cross-origin preflight came back without Access-Control-Allow-Origin, so the endpoint is reachable from native clients only — code running in a web page is stopped by the browser before a request is ever sent.

Tools

check_email_domainget_dmarc_recordget_mx_recordsget_spf_record

Contract history

24 Aug 2026v1.0.0first recorded contract

Get alerted when this contract changes

Depend on this server? Leave an email and get a message when a probe records a change — a tool removed, an argument newly required, an enum narrowed. Alerts are being built; signing up is what tells us to hurry.

Prefer a feed reader? This page's contract changes are also an Atom feed.

Status badge

Status for a README, from the last probe — cached an hour, so up to seven hours behind the endpoint. Links back to this page.

[![MCP status](https://mcpi.app/servers/email-check/badge.svg)](https://mcpi.app/servers/email-check)