# ai.kaiv/email-check (remote · api.kaiv.ai)

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

- Trust score: 89/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `api.kaiv.ai`: 89/100 (this document), [markdown](https://verifymcp.io/servers/ai-kaiv-email-check/api-bridge-mcp-email-check-b6ab5250.md), [page](https://verifymcp.io/servers/ai-kaiv-email-check/api-bridge-mcp-email-check-b6ab5250)

## Channel facts

- Endpoint: `https://api.kaiv.ai/api/bridge/mcp/email-check-b6ab5250`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 83/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 79/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 622 tokens (~155/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the ai.kaiv/email-check MCP server?

ai.kaiv/email-check is a hosted endpoint at https://api.kaiv.ai/api/bridge/mcp/email-check-b6ab5250, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

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

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

```bash
openclaw mcp add ai-kaiv-email-check --url 'https://api.kaiv.ai/api/bridge/mcp/email-check-b6ab5250' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-kaiv-email-check:
    url: "https://api.kaiv.ai/api/bridge/mcp/email-check-b6ab5250"
```

### Netclaw

```json
{
  "McpServers": {
    "ai-kaiv-email-check": {
      "Transport": "http",
      "Url": "https://api.kaiv.ai/api/bridge/mcp/email-check-b6ab5250"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ai-kaiv-email-check -t streamable-http -u 'https://api.kaiv.ai/api/bridge/mcp/email-check-b6ab5250'
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 89, 0)

- [security] Stability: 0.97 → pass

### 2026-09-19 (score 89, +1)

No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-16 (score 88, +1)

No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-14 (score 87, +1)

No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-12 (score 86, +1)

No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-10 (score 85, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-08 (score 84, +1)

No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-06 (score 83, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (4)

### `check_email_domain` (~144 tokens)

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 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.

Input parameters:

- `domain` (string, required): Domain to check, e.g. "example.com". A full email address is accepted and the domain is taken from it.

Output parameters:

- `can_receive_mail` (boolean): False when the domain publishes no MX records.
- `checked_at` (string)
- `dmarc` (object)
- `domain` (string)
- `findings` (array): One line per specific problem; empty when the domain is correctly configured.
- `mx` (object)
- `spf` (object)
- `spoofable` (boolean): True unless DMARC is present AND at an enforcing policy. Deliberately conservative: without enforcement a receiver has no instruction to reject forged mail, however good the SPF record is.
- `summary` (string): Plain-language verdict.

### `get_dmarc_record` (~163 tokens)

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 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.

Input parameters:

- `domain` (string, required): Domain to check, e.g. "example.com". A full email address is accepted and the domain is taken from it.

Output parameters:

- `all_records` (array): Present only when more than one DMARC record exists.
- `domain` (string)
- `found` (boolean)
- `meaning` (string)
- `multiple_records` (boolean): RFC 7489 requires receivers to apply NO policy when more than one record exists.
- `percent` (integer): The pct= tag; defaults to 100.
- `policy` (string): "ignored" means duplicate records cancelled the policy out.
- `protects` (boolean): False for p=none (monitoring only) and for duplicate records.
- `record` (string)

### `get_mx_records` (~99 tokens)

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 picture.

Input parameters:

- `domain` (string, required): Domain to check, e.g. "example.com". A full email address is accepted and the domain is taken from it.

Output parameters:

- `can_receive_mail` (boolean)
- `domain` (string)
- `found` (boolean): Whether any MX record exists.
- `hosts` (array): MX hosts, lowest priority first.

### `get_spf_record` (~116 tokens)

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. Use when diagnosing why mail from a domain is being rejected or marked.

Input parameters:

- `domain` (string, required): Domain to check, e.g. "example.com". A full email address is accepted and the domain is taken from it.

Output parameters:

- `domain` (string)
- `found` (boolean)
- `meaning` (string): What the qualifier means in practice.
- `multiple_records` (boolean): More than one SPF record: receivers treat this as permerror, so SPF effectively fails.
- `qualifier` (string): The qualifier on the `all` mechanism.
- `record` (string): The raw SPF TXT record, or null when absent.
- `strict` (boolean): True only for `-all`, the one strict answer.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ai-kaiv-email-check/api-bridge-mcp-email-check-b6ab5250#diagnostics

## Score history

- 2026-09-20: 89
- 2026-09-19: 89
- 2026-09-18: 88
- 2026-09-17: 88
- 2026-09-16: 88
- 2026-09-15: 87
- 2026-09-14: 87
- 2026-09-13: 86
- 2026-09-12: 86
- 2026-09-11: 85
- 2026-09-10: 85
- 2026-09-09: 84
- 2026-09-08: 84
- 2026-09-07: 83
- 2026-09-06: 83
- 2026-09-05: 82
- 2026-09-04: 82
- 2026-09-03: 81
- 2026-09-02: 81
- 2026-09-01: 79
- 2026-08-31: 79
- 2026-08-30: 78
- 2026-08-29: 78
- 2026-08-28: 77
- 2026-08-27: 77
- 2026-08-26: 77
- 2026-08-25: 75
- 2026-08-24: 74
- 2026-08-23: 74
- 2026-08-22: 72

## Common questions

### What is the ai.kaiv/email-check MCP server?

ai.kaiv/email-check is an MCP server listed in the public MCP registry as ai.kaiv/email-check. Email posture for any domain: can it receive mail, can it be spoofed? MX, SPF and DMARC. This page covers its hosted endpoint (https://api.kaiv.ai/api/bridge/mcp/email-check-b6ab5250).

### Is the ai.kaiv/email-check MCP server safe to use?

ai.kaiv/email-check scores 89 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the ai.kaiv/email-check MCP server expose?

ai.kaiv/email-check exposes 4 tools: check_email_domain, get_dmarc_record, get_mx_records, get_spf_record. Their descriptions and schemas cost roughly 522 tokens of context every time the server is loaded.

### Does the ai.kaiv/email-check MCP server require authentication?

No. We connected to ai.kaiv/email-check without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the ai.kaiv/email-check MCP server still maintained?

ai.kaiv/email-check is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://api.kaiv.ai/api/bridge/mcp/email-check-b6ab5250
- Changelog RSS feed: https://verifymcp.io/servers/ai-kaiv-email-check/api-bridge-mcp-email-check-b6ab5250.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-kaiv-email-check/api-bridge-mcp-email-check-b6ab5250.json
- HTML version of this page: https://verifymcp.io/servers/ai-kaiv-email-check/api-bridge-mcp-email-check-b6ab5250