Email Check
by kaiv.ai in Email & messaging
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-b6ab5250
Last 30 days
- Uptime
- 100%
- Response time
- 162 ms typical, 162 ms slowest 5%
- Last check
- 4 h ago
- Next check
- in 2 h
How to call it
Add it to any MCP client that supports remote servers.
{
"mcpServers": {
"email-check": {
"type": "http",
"url": "https://api.kaiv.ai/api/bridge/mcp/email-check-b6ab5250"
}
}
}4 tools
- 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
- 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
- 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 p
- 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.
Security scan
- No findings. We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.
Recent checks
| When | Result | HTTP | Time |
|---|---|---|---|
| 4 h ago | Passed | 200 | 221 ms |
| 12 h ago | Passed | 200 | 162 ms |
| 21 h ago | Passed | 200 | 74 ms |