MailAuth Audit (Email Deliverability)
REMOTE · MAILAUTH-AL6BXCNGIA-UE.A.RUN.APP
Audits a domain's SPF, DKIM, DMARC and MX for spoofing risk and deliverability. $1.50/call via x402.
Available components
Last scanned (21 hours ago)
Scores higher than 59% of remote servers
Reachable. Last reached 21 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 Security74
- 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 check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability73
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 539 tokens (~269/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (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.
- 21 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Nov 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.
- 18 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 17 Nov 26 71
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 21 Nov 2026 · Probed https://mailauth-al6bxcngia-ue.a.run.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.a.run.app | CN=WE2,O=Google Trust Services,C=US | 3 Nov 2026 | 26 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | f668c9036838957b095b05d18ab2228d |
| SANs: *.a.run.app, run.app, *.africa-south1.run.app, *.asia-east1.run.app, *.asia-east2.run.app, *.asia-northeast1.run.app, *.asia-northeast2.run.app, *.asia-northeast3.run.app, *.asia-south1.run.app, *.asia-south2.run.app, *.asia-southeast1.run.app, *.asia-southeast2.run.app and 93 more | ||||||
| CN=WE2,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 | 7ff32d6b409d15d5965b05873a7c72e0 |
| 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 insecure
Validation of mailauth-al6bxcngia-ue.a.run.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| app. | DS published | 23684 | 8 | Verified |
| run.app. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
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://mailauth-al6bxcngia-ue.a.run.app/mcp | Verified | 200 | |
| http (plaintext) | http://mailauth-al6bxcngia-ue.a.run.app/mcp | HTTPS enforced | 302 | https://mailauth-al6bxcngia-ue.a.run.app/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 →
audit_mailauth ~397
Full email deliverability audit of a domain (bare domain, e.g. example.com). Resolves the domain's mail DNS over DNS-over-HTTPS and runs 12 weighted checks: MX presence and redundancy, SPF presence, validity (single record, <=10 DNS lookups), and terminal policy (-all vs ~all vs ?all), DMARC presence, enforcement policy (p=reject/quarantine/none, pct), and aggregate reporting (rua), DKIM discoverability at 10 common selectors, MTA-STS, TLS-RPT, and BIMI. These records decide whether receivers can verify mail claiming to be from the domain: no DMARC (or p=none) means the domain is trivially spoofable by anyone, and broken SPF/DKIM alignment is why legitimate mail lands in spam. Returns machine-readable JSON: 0-100 score, A-F grade, a spoofing/deliverability risk level (Low/Moderate/Elevated/High) with the failing spoofing-class checks named, per-check pass/partial/fail/unknown with evidence, the observed records (MX hosts, SPF record, DMARC policy/pct, DKIM selectors found, MTA-STS/TLS-RPT/BIMI presence), and the top 3 prioritized fixes. HONEST LIMITS: this is a DNS snapshot at scan time; DKIM is probed at common selectors only (a custom selector reads as undiscoverable, not absent); no mail is sent, and inbox placement is not guaranteed. Cost: $1.50 USDC on Base per call, paid via x402 — the caller's agent pays from its owner's approved wallet; no API key needed. Use this before launching outbound from a domain, after any DNS change, or to triage a spoofing/spam-folder problem.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Bare domain to audit, e.g. example.com |
No output schema declared.
No examples provided.
audit_mailauth_lite ~142
FREE lite email deliverability audit of a domain (bare domain, e.g. example.com). Runs the same 12 SPF/DKIM/DMARC/MX checks as audit_mailauth but returns top-line results only: 0-100 score, A-F grade, spoofing/deliverability risk level, check counts, and the titles of the top gaps — the observed records and per-check evidence are capped. Use this to triage whether a domain needs the full audit_mailauth report, or call audit_mailauth directly for the complete evidence-backed scan.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Bare domain to audit, e.g. example.com |
No output schema declared.
No examples provided.
How do I install the MailAuth Audit (Email Deliverability) MCP server?
MailAuth Audit (Email Deliverability) is a hosted endpoint at https://mailauth-al6bxcngia-ue.a.run.app/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 · mailauth-al6bxcngia-ue.a.run.app
claude mcp add --transport http theharrisontruong-web-mailauth-audit 'https://mailauth-al6bxcngia-ue.a.run.app/mcp'
What is the MailAuth Audit (Email Deliverability) MCP server?
MailAuth Audit (Email Deliverability) is an MCP server listed in the public MCP registry as io.github.theharrisontruong-web/mailauth-audit. Audits a domain's SPF, DKIM, DMARC and MX for spoofing risk and deliverability. $1.50/call via x402. This page covers its hosted endpoint (https://mailauth-al6bxcngia-ue.a.run.app/mcp).
Is the MailAuth Audit (Email Deliverability) MCP server safe to use?
MailAuth Audit (Email Deliverability) scores 73 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 MailAuth Audit (Email Deliverability) MCP server expose?
MailAuth Audit (Email Deliverability) exposes 2 tools: audit_mailauth, audit_mailauth_lite. Their descriptions and schemas cost roughly 539 tokens of context every time the server is loaded.
Does the MailAuth Audit (Email Deliverability) MCP server require authentication?
No. We connected to MailAuth Audit (Email Deliverability) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the MailAuth Audit (Email Deliverability) MCP server still maintained?
MailAuth Audit (Email Deliverability) is still listed as active in the MCP registry. We last reached this channel on 21 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 MailAuth Audit (Email Deliverability) MCP server?
VerifyMCP ran 13 checks on MailAuth Audit (Email Deliverability), 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.