kaiv/email-check
latest · 1.0.0Email posture for any domain: can it receive mail, can it be spoofed? MX, SPF and DMARC.
- MCP registry
- ai.kaiv/email-check
Install
claude mcp add --transport http ai-kaiv-email-check https://api.kaiv.ai/api/bridge/mcp/email-check-b6ab5250/mcp confirms it's connected.
Or add it manually in ~/.cursor/mcp.json:
{
"mcpServers": {
"ai-kaiv-email-check": {
"url": "https://api.kaiv.ai/api/bridge/mcp/email-check-b6ab5250"
}
}
}In claude_desktop_config.json (Settings → Developer → Edit Config), then restart:
{
"mcpServers": {
"ai-kaiv-email-check": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://api.kaiv.ai/api/bridge/mcp/email-check-b6ab5250"
]
}
}
}Endpoint, any MCP client:
https://api.kaiv.ai/api/bridge/mcp/email-check-b6ab5250Community score
Community52/ 100
from web signals · no reviews yet (community v3)
- Web signals (ecosystem baseline)52/100 · 100% of the weight
Used it? Rate v1.0.0
No reviews yet — be the first.
What the web says
Ecosystem baseline52/ 100
Objective public usage & activity (formula v3) — the community score's web-signals input, and its own sort.
GitHub
Nothing collected from GitHub yet.
Packages
No package-registry data collected yet.
Listed on
Not yet found on other registries or list sites.
Mentions
No public discussion scraped yet.
Docs & liveness
- Endpoint status · 26 days ago
- Live
- Response time · 26 days ago
- 32 ms
- Listing completeness · 26 days ago
- 100%
Version history1
- 1.0.0release date unknown
Details
- Transport
- streamable-http
- Status
- listed
- Source
- Imported from the MCP registry