Connect

8 clients · secrets stay placeholders

JSON (mcpServers)Claude CodeCodexOpenCodeCursorVS CodeGemini CLIGoose

{
  "mcpServers": {
    "email-check": {
      "type": "http",
      "url": "https://api.kaiv.ai/api/bridge/mcp/email-check-b6ab5250"
    }
  }
}

claude mcp add --transport http email-check https://api.kaiv.ai/api/bridge/mcp/email-check-b6ab5250

[mcp_servers.email-check]
url = "https://api.kaiv.ai/api/bridge/mcp/email-check-b6ab5250"

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "email-check": {
      "type": "remote",
      "url": "https://api.kaiv.ai/api/bridge/mcp/email-check-b6ab5250",
      "enabled": true
    }
  }
}

{
  "mcpServers": {
    "email-check": {
      "type": "http",
      "url": "https://api.kaiv.ai/api/bridge/mcp/email-check-b6ab5250"
    }
  },
  "deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=email-check&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vYXBpLmthaXYuYWkvYXBpL2JyaWRnZS9tY3AvZW1haWwtY2hlY2stYjZhYjUyNTAifQ%3D%3D"
}

{
  "servers": {
    "email-check": {
      "type": "http",
      "url": "https://api.kaiv.ai/api/bridge/mcp/email-check-b6ab5250"
    }
  }
}

{
  "mcpServers": {
    "email-check": {
      "httpUrl": "https://api.kaiv.ai/api/bridge/mcp/email-check-b6ab5250"
    }
  }
}

extensions:
  "email-check":
    enabled: true
    name: "email-check"
    type: streamable_http
    uri: "https://api.kaiv.ai/api/bridge/mcp/email-check-b6ab5250"
    timeout: 300

Quality 100 / 100strong

protocol100 · weight 25

pass
protocol.modernsupports 2026-07-28 (server/discover)
pass
protocol.statelessanswers without a session
pass
protocol.transportstreamable HTTP
pass
protocol.list_ttltool list is cacheable (ttlMs 60000)

authorizationn/a · weight 15

n/a
auth.prm, auth.as_metadata, auth.cimdno remote uses OAuth
n/a
auth.secret_in_urlno templated URL

tool hygiene100 · weight 30

pass
tools.descriptionsevery tool has a description
pass
tools.description_lengthdescriptions are concise
pass
tools.schemasevery tool has an object input schema
pass
tools.annotations4 of 4 tools declare readOnlyHint or destructiveHint
pass
tools.directory_hintsevery tool declares readOnlyHint, destructiveHint, idempotentHint and openWorldHint
pass
tools.token_costabout 795 tokens to load every tool
pass
tools.api_dumptools are not a one-to-one API dump

stability100 · weight 15

pass
stability.changesno tool changes in 30 days
pass
stability.rug_pullno tool changed its meaning under the same name

dependenciesn/a · weight 15

n/a
deps.known_vulns, deps.mcp_sdk_version, deps.resolvableno npm or PyPI package

4 tools, about 795 tokens to load them all · tool set 50efc6c9bc91 · checked 2026-10-20 17:02 UTC

Tool changes

No tool definition changes recorded. A server's first observation is its baseline; later probes record what changes.

Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.

Trust 76 / 100

no-repository

provenance45

liveness97

freshness85

hygiene80

+dns-namespace +reachable +uptime-93% ~updated-60d-ago -no-repository

Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.

Endpoints

remote	auth	reachable	uptime 30d	p50	protocol	last ok
`https://api.kaiv.ai/api/bridge/mcp/email-check-b6ab5250` streamable-http	none	yes	93%	336 ms	2026-07-28, 2025-11-25, 2025-06-18, 2025-03-26, 2024-11-05	2026-10-20

Tools (4)

`check_email_domain`read-only	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.
`get_dmarc_record`read-only	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.
`get_mx_records`read-only	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.
`get_spf_record`read-only	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.

Schemas: list_tools.

Similar MCP servers

More from ai.kaiv

And 2 more from this publisher.

Official server.json

{
  "name": "ai.kaiv/email-check",
  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
  "remotes": [
    {
      "url": "https://api.kaiv.ai/api/bridge/mcp/email-check-b6ab5250",
      "type": "streamable-http"
    }
  ],
  "version": "1.0.0",
  "description": "Email posture for any domain: can it receive mail, can it be spoofed? MX, SPF and DMARC."
}