scan.mx Email Diagnostics
REMOTE · API.SCAN.MX
Email deliverability check: MX, SPF, DKIM, DMARC, blacklists, MTA-STS, DNSSEC, BIMI. Graded, no key.
Available components
Last scanned (21 hours ago)
Scores higher than 95% of remote servers
Reachable. Last reached 6 Nov 2026.
Category Security
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. How we score → Why this is hard to score →
Endpoint Security77
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability83
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 712 tokens (~79/item across 9 items; 9 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 13 Oct 26 0
- Schema quality: 526 → 712 ▼ functional
- New tool “check_bimi” functional
- New tool “check_dnssec” functional
- New tool “check_mta_sts” functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 18 Aug 26 0
- Tool “check_domain” rewrote its description, which is the text the model reads security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 6 Nov 2026 · Probed https://api.scan.mx/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=scan.mx | CN=WE1,O=Google Trust Services,C=US | 2 Nov 2026 | 31 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | d5194cbf5538ae3c0ea6108da6f7fef5 |
| SANs: scan.mx, api.scan.mx, *.api.scan.mx | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of api.scan.mx. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| mx. | DS published | 43850 | 8 | Verified |
| scan.mx. | DS published | 2371 | 13 | Verified |
| api.scan.mx. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.scan.mx/mcp | Verified | 200 | |
| http (plaintext) | http://api.scan.mx/mcp | HTTPS enforced | 301 | https://api.scan.mx/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_bimi Check BIMI ~64
Check the domain BIMI record at default._bimi: the SVG logo URL, the VMC/CMC certificate, and the DMARC enforcement BIMI needs.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | The domain to check, e.g. example.com. No scheme or path. |
| Name | Type | Req | Description |
|---|---|---|---|
| checks | array | – | – |
| created_at | number | – | – |
| domain | string | yes | – |
| 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 | – | – |
No examples provided.
check_blacklist Check blacklists ~71
Check whether the domain and its mail server IPs are listed on the Spamhaus (ZEN, DBL, ZRD, AuthBL), SpamCop, GBUdb and PSBL blocklists.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | The domain to check, e.g. example.com. No scheme or path. |
| Name | Type | Req | Description |
|---|---|---|---|
| checks | array | – | – |
| created_at | number | – | – |
| domain | string | yes | – |
| 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 | – | – |
No examples provided.
check_dkim Check DKIM ~92
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.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | 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"). |
| Name | Type | Req | Description |
|---|---|---|---|
| checks | array | – | – |
| created_at | number | – | – |
| domain | string | yes | – |
| 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 | – | – |
No examples provided.
check_dmarc Check DMARC ~58
Check the domain DMARC policy at _dmarc: presence, policy strength (none/quarantine/reject), and reporting.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | The domain to check, e.g. example.com. No scheme or path. |
| Name | Type | Req | Description |
|---|---|---|---|
| checks | array | – | – |
| created_at | number | – | – |
| domain | string | yes | – |
| 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 | – | – |
No examples provided.
check_dnssec Check DNSSEC and DNS health ~56
Check DNSSEC validation and DNS health: delegation, nameserver count, SOA, and reverse DNS of the mail servers.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | The domain to check, e.g. example.com. No scheme or path. |
| Name | Type | Req | Description |
|---|---|---|---|
| checks | array | – | – |
| created_at | number | – | – |
| domain | string | yes | – |
| 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 | – | – |
No examples provided.
check_domain Full email deliverability check ~196
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, where specific weaknesses cap the grade), 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.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| checks | array | – | – |
| created_at | number | – | – |
| domain | string | yes | – |
| 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 | – | – |
No examples provided.
check_mta_sts Check MTA-STS ~66
Check the domain MTA-STS policy (_mta-sts TXT and the HTTPS policy file, mode and MX coverage) and its TLS-RPT reporting record.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | The domain to check, e.g. example.com. No scheme or path. |
| Name | Type | Req | Description |
|---|---|---|---|
| checks | array | – | – |
| created_at | number | – | – |
| domain | string | yes | – |
| 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 | – | – |
No examples provided.
check_mx Check MX records ~56
Check the MX records of a domain: presence, hostnames, resolution, null-MX, and common misconfigurations.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | The domain to check, e.g. example.com. No scheme or path. |
| Name | Type | Req | Description |
|---|---|---|---|
| checks | array | – | – |
| created_at | number | – | – |
| domain | string | yes | – |
| 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 | – | – |
No examples provided.
check_spf Check SPF ~53
Check the domain SPF policy: presence, syntax, the all qualifier, and the 10-lookup limit.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | The domain to check, e.g. example.com. No scheme or path. |
| Name | Type | Req | Description |
|---|---|---|---|
| checks | array | – | – |
| created_at | number | – | – |
| domain | string | yes | – |
| 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 | – | – |
No examples provided.
How do I install the scan.mx Email Diagnostics MCP server?
scan.mx Email Diagnostics is a hosted endpoint at https://api.scan.mx/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.
remote · api.scan.mx
claude mcp add --transport http mx-scan-diagnostics 'https://api.scan.mx/mcp'
What is the scan.mx Email Diagnostics MCP server?
scan.mx Email Diagnostics is an MCP server listed in the public MCP registry as mx.scan/diagnostics. Email deliverability check: MX, SPF, DKIM, DMARC, blacklists, MTA-STS, DNSSEC, BIMI. Graded, no key. This page covers its hosted endpoint (https://api.scan.mx/mcp).
Is the scan.mx Email Diagnostics MCP server safe to use?
scan.mx Email Diagnostics scores 88 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 scan.mx Email Diagnostics MCP server expose?
scan.mx Email Diagnostics exposes 9 tools: check_domain, check_mx, check_spf, check_dmarc, check_blacklist, and 4 more. Their descriptions and schemas cost roughly 712 tokens of context every time the server is loaded.
Does the scan.mx Email Diagnostics MCP server require authentication?
No. We connected to scan.mx Email Diagnostics without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the scan.mx Email Diagnostics MCP server still maintained?
scan.mx Email Diagnostics is still listed as active in the MCP registry. We last reached this channel on 6 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the scan.mx Email Diagnostics MCP server?
VerifyMCP ran 13 checks on scan.mx Email Diagnostics, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.