scan.mx Email Diagnostics
REMOTE · API.SCAN.MX · SCANNED AUG 3
Check email deliverability for a domain: MX, SPF, DKIM, DMARC, blacklists. Graded, no key.
Available components
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 →
Endpoint Security60
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- 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 Usability77
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 518 tokens (~86/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · api.scan.mx
claude mcp add --transport http mx-scan-diagnostics https://api.scan.mx/mcp
[mcp_servers.mx-scan-diagnostics] url = "https://api.scan.mx/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"mx-scan-diagnostics": {
"type": "remote",
"url": "https://api.scan.mx/mcp",
"enabled": true
}
}
} openclaw mcp add mx-scan-diagnostics --url https://api.scan.mx/mcp --transport streamable-http
mcp_servers:
mx-scan-diagnostics:
url: "https://api.scan.mx/mcp" {
"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.
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.
- 2 Aug 26 +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.
- 31 Jul 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
- 30 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 28 Jul 26 +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.
- 27 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 64
First indexed and scored.
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 3 Aug 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 | 7 Jul 2026 | 5 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | 2633d568688e10e31316166682db80c0 |
| 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 |
DNSSEC secure
Validation of api.scan.mx. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| mx. | present | 43850 | 8 | Verified |
| scan.mx. | present | 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 |
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.
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_domain Full email deliverability check ~188
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.
| 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_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.