# scan.mx Email Diagnostics (remote · api.scan.mx)

Check email deliverability for a domain: MX, SPF, DKIM, DMARC, blacklists. Graded, no key.

- Trust score: 68/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `api.scan.mx`: 68/100 (this document), [markdown](https://verifymcp.io/servers/mx-scan-diagnostics/api.md), [page](https://verifymcp.io/servers/mx-scan-diagnostics/api)

## Channel facts

- Endpoint: `https://api.scan.mx/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-08-03.

- **Endpoint Security**: 60/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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**: 77/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 518 tokens (~86/item across 6 items; 6 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **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.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http mx-scan-diagnostics https://api.scan.mx/mcp
```

### Codex

```toml
[mcp_servers.mx-scan-diagnostics]
url = "https://api.scan.mx/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "mx-scan-diagnostics": {
      "type": "remote",
      "url": "https://api.scan.mx/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add mx-scan-diagnostics --url https://api.scan.mx/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  mx-scan-diagnostics:
    url: "https://api.scan.mx/mcp"
```

### Other

```json
{
  "mcpServers": {
    "mx-scan-diagnostics": {
      "type": "http",
      "url": "https://api.scan.mx/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-08-02 (score 68, +1)

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

### 2026-07-31 (score 67, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 67, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-28 (score 66, +1)

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

### 2026-07-27 (score 65, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 64)

First indexed and scored.

## MCP tools (6)

### `check_domain` (~188 tokens)

Full email deliverability check

Run the full email and DNS deliverability check for a domain: MX, SPF, DKIM, DMARC, DNS health, provider detection, and blacklists. Returns a letter grade (A to F), a 0 to 100 score, and every individual check with its RFC reference. Set include_smtp to also run a live SMTP probe of the mail servers: the probe is non-blocking, so when smtp_status is "pending" or "running" call this tool again (poll_after_seconds hints how long to wait) until smtp_status is "complete" and the SMTP checks appear in checks.

Input parameters:

- `domain` (string, required): The domain to check, e.g. example.com. No scheme or path.
- `include_smtp` (boolean): Also run a live SMTP connectivity probe of the MX hosts. Non-blocking: poll by re-calling until smtp_status is complete.

Output parameters:

- `checks` (array)
- `created_at` (number)
- `domain` (string)
- `expires_at` (number)
- `grade` (string)
- `permalink` (string)
- `poll_after_seconds` (number)
- `provider`
- `score` (number)
- `sections` (object)
- `selector` (string)
- `smtp_note` (string)
- `smtp_status` (string)
- `updated_at` (number)

### `check_mx` (~56 tokens)

Check MX records

Check the MX records of a domain: presence, hostnames, resolution, null-MX, and common misconfigurations.

Input parameters:

- `domain` (string, required): The domain to check, e.g. example.com. No scheme or path.

Output parameters:

- `checks` (array)
- `created_at` (number)
- `domain` (string)
- `expires_at` (number)
- `grade` (string)
- `permalink` (string)
- `poll_after_seconds` (number)
- `provider`
- `score` (number)
- `sections` (object)
- `selector` (string)
- `smtp_note` (string)
- `smtp_status` (string)
- `updated_at` (number)

### `check_spf` (~53 tokens)

Check SPF

Check the domain SPF policy: presence, syntax, the all qualifier, and the 10-lookup limit.

Input parameters:

- `domain` (string, required): The domain to check, e.g. example.com. No scheme or path.

Output parameters:

- `checks` (array)
- `created_at` (number)
- `domain` (string)
- `expires_at` (number)
- `grade` (string)
- `permalink` (string)
- `poll_after_seconds` (number)
- `provider`
- `score` (number)
- `sections` (object)
- `selector` (string)
- `smtp_note` (string)
- `smtp_status` (string)
- `updated_at` (number)

### `check_dmarc` (~58 tokens)

Check DMARC

Check the domain DMARC policy at _dmarc: presence, policy strength (none/quarantine/reject), and reporting.

Input parameters:

- `domain` (string, required): The domain to check, e.g. example.com. No scheme or path.

Output parameters:

- `checks` (array)
- `created_at` (number)
- `domain` (string)
- `expires_at` (number)
- `grade` (string)
- `permalink` (string)
- `poll_after_seconds` (number)
- `provider`
- `score` (number)
- `sections` (object)
- `selector` (string)
- `smtp_note` (string)
- `smtp_status` (string)
- `updated_at` (number)

### `check_blacklist` (~71 tokens)

Check blacklists

Check whether the domain and its mail server IPs are listed on the Spamhaus (ZEN, DBL, ZRD, AuthBL), SpamCop, GBUdb and PSBL blocklists.

Input parameters:

- `domain` (string, required): The domain to check, e.g. example.com. No scheme or path.

Output parameters:

- `checks` (array)
- `created_at` (number)
- `domain` (string)
- `expires_at` (number)
- `grade` (string)
- `permalink` (string)
- `poll_after_seconds` (number)
- `provider`
- `score` (number)
- `sections` (object)
- `selector` (string)
- `smtp_note` (string)
- `smtp_status` (string)
- `updated_at` (number)

### `check_dkim` (~92 tokens)

Check DKIM

Check DKIM signing keys for a domain. Without a selector, common provider selectors are probed. Pass an explicit selector to look up that exact key at selector._domainkey.

Input parameters:

- `domain` (string, required): The domain to check, e.g. example.com. No scheme or path.
- `selector` (string): An explicit DKIM selector to look up (e.g. "google", "s1").

Output parameters:

- `checks` (array)
- `created_at` (number)
- `domain` (string)
- `expires_at` (number)
- `grade` (string)
- `permalink` (string)
- `poll_after_seconds` (number)
- `provider`
- `score` (number)
- `sections` (object)
- `selector` (string)
- `smtp_note` (string)
- `smtp_status` (string)
- `updated_at` (number)

## Diagnostics

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

## Score history

- 2026-08-03: 68
- 2026-08-02: 68
- 2026-08-01: 67
- 2026-07-31: 67
- 2026-07-30: 67
- 2026-07-29: 66
- 2026-07-28: 66
- 2026-07-27: 65
- 2026-07-26: 64

## Links

- Remote endpoint: https://api.scan.mx/mcp
- Website: https://scan.mx/
- Changelog RSS feed: https://verifymcp.io/servers/mx-scan-diagnostics/api/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/mx-scan-diagnostics/api/changelog.json
- HTML version of this page: https://verifymcp.io/servers/mx-scan-diagnostics/api