# MX Verdict (remote · mxverdict.com)

Free, read-only email and DNS checks: SPF, DKIM, DMARC, MX, DNS records, blocklists, domain health.

- Trust score: 90/100 (high trust)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `mxverdict.com`: 90/100 (this document), [markdown](https://verifymcp.io/servers/com-mxverdict-mxverdict/mxverdict.md), [page](https://verifymcp.io/servers/com-mxverdict-mxverdict/mxverdict)

## Channel facts

- Endpoint: `https://mxverdict.com/mcp`
- 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-11-05.

- **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**: 81/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 660 tokens (~94/item across 7 items; 7 tools + 0 resources), lean.
  - 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.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the MX Verdict MCP server?

MX Verdict is a hosted endpoint at https://mxverdict.com/mcp, 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 com-mxverdict-mxverdict 'https://mxverdict.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-mxverdict-mxverdict": {
      "url": "https://mxverdict.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-mxverdict-mxverdict": {
      "type": "http",
      "url": "https://mxverdict.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-mxverdict-mxverdict]
url = "https://mxverdict.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-mxverdict-mxverdict": {
      "type": "remote",
      "url": "https://mxverdict.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-mxverdict-mxverdict --url 'https://mxverdict.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-mxverdict-mxverdict:
    url: "https://mxverdict.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-mxverdict-mxverdict": {
      "Transport": "http",
      "Url": "https://mxverdict.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-mxverdict-mxverdict -t streamable-http -u 'https://mxverdict.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-mxverdict-mxverdict": {
      "type": "http",
      "url": "https://mxverdict.com/mcp"
    }
  }
}
```

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-10-28 (score 90, +1)

- [security] Stability: 0.97 → pass

### 2026-10-26 (score 89, +1)

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

### 2026-10-24 (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-10-21 (score 87, +1)

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

### 2026-10-19 (score 86, +1)

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

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

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

### 2026-10-15 (score 84, +1)

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

### 2026-10-13 (score 83, +1)

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

## MCP tools (7)

### `check_email_domain` (~82 tokens)

Email domain health check

Check everything about a domain's email setup in one call: SPF, DMARC, MX, DKIM on common selectors, domain blocklists, MTA-STS, TLS-RPT and BIMI. Use it for a general question such as "is email set up correctly for example.com".

Input parameters:

- `domain` (string, required): Domain name, for example example.com.

### `check_spf` (~64 tokens)

SPF check

Check a domain's SPF record: whether it exists and is valid, how many of the 10 allowed DNS lookups it uses, and how its all mechanism treats mail from servers that are not listed.

Input parameters:

- `domain` (string, required): Domain name, for example example.com.

### `check_dkim` (~110 tokens)

DKIM check

Check a domain's DKIM public keys in DNS. With a selector (the s= tag of a DKIM-Signature header), checks that selector's key; without one, probes common selector names. Finding no key on common names does not prove DKIM is missing: selectors cannot be listed from DNS.

Input parameters:

- `domain` (string, required): Domain name, for example example.com.
- `selector` (string): DKIM selector, for example google or selector1. Leave out to probe common selectors.

### `check_dmarc` (~56 tokens)

DMARC check

Check a domain's DMARC record: whether it exists and is valid, its policy (none, quarantine or reject), alignment, and where reports are sent.

Input parameters:

- `domain` (string, required): Domain name, for example example.com.

### `lookup_mx` (~55 tokens)

MX lookup

Look up a domain's MX records (its incoming mail servers), their IP addresses and reverse DNS. DNS only: it does not connect to the mail servers.

Input parameters:

- `domain` (string, required): Domain name, for example example.com.

### `dns_lookup` (~101 tokens)

DNS lookup

Look up DNS records of a name. Type ALL (the default) queries A, AAAA, CNAME, MX, NS, TXT, SOA and CAA; any single type can be asked for. An IP address gives its reverse DNS (PTR) lookup.

Input parameters:

- `name` (string, required): Domain name or IP address, for example example.com or _dmarc.example.com.
- `type` (string): Record type; ALL when left out.

### `check_blacklist` (~69 tokens)

Blacklist check

Check whether an IP address or a domain is listed on public DNS blocklists (DNSBLs). A domain is checked on domain blocklists only; to check a mail server, give its IP address.

Input parameters:

- `target` (string, required): One IPv4 or IPv6 address, or one domain name.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-mxverdict-mxverdict/mxverdict#diagnostics

## Score history

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

## Common questions

### What is the MX Verdict MCP server?

MX Verdict is an MCP server listed in the public MCP registry as com.mxverdict/mxverdict. Free, read-only email and DNS checks: SPF, DKIM, DMARC, MX, DNS records, blocklists, domain health. This page covers its hosted endpoint (https://mxverdict.com/mcp).

### Is the MX Verdict MCP server safe to use?

MX Verdict scores 90 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 MX Verdict MCP server expose?

MX Verdict exposes 7 tools: check_email_domain, check_spf, check_dkim, check_dmarc, lookup_mx, and 2 more. Their descriptions and schemas cost roughly 537 tokens of context every time the server is loaded.

### Does the MX Verdict MCP server require authentication?

No. We connected to MX Verdict without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the MX Verdict MCP server still maintained?

MX Verdict is still listed as active in the MCP registry. We last reached this channel on 5 November 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://mxverdict.com/mcp
- Website: https://mxverdict.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-mxverdict-mxverdict/mxverdict.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-mxverdict-mxverdict/mxverdict.json
- HTML version of this page: https://verifymcp.io/servers/com-mxverdict-mxverdict/mxverdict