# 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.

- Trust score: 73/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `mailauth-al6bxcngia-ue.a.run.app`: 73/100 (this document), [markdown](https://verifymcp.io/servers/theharrisontruong-web-mailauth-audit/mailauth-al6bxcngia-ue.md), [page](https://verifymcp.io/servers/theharrisontruong-web-mailauth-audit/mailauth-al6bxcngia-ue)

## Channel facts

- Endpoint: `https://mailauth-al6bxcngia-ue.a.run.app/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-21.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 73/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 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.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### 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.

### Claude

```bash
claude mcp add --transport http theharrisontruong-web-mailauth-audit 'https://mailauth-al6bxcngia-ue.a.run.app/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "theharrisontruong-web-mailauth-audit": {
      "url": "https://mailauth-al6bxcngia-ue.a.run.app/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "theharrisontruong-web-mailauth-audit": {
      "type": "http",
      "url": "https://mailauth-al6bxcngia-ue.a.run.app/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.theharrisontruong-web-mailauth-audit]
url = "https://mailauth-al6bxcngia-ue.a.run.app/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "theharrisontruong-web-mailauth-audit": {
      "type": "remote",
      "url": "https://mailauth-al6bxcngia-ue.a.run.app/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add theharrisontruong-web-mailauth-audit --url 'https://mailauth-al6bxcngia-ue.a.run.app/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  theharrisontruong-web-mailauth-audit:
    url: "https://mailauth-al6bxcngia-ue.a.run.app/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "theharrisontruong-web-mailauth-audit": {
      "Transport": "http",
      "Url": "https://mailauth-al6bxcngia-ue.a.run.app/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add theharrisontruong-web-mailauth-audit -t streamable-http -u 'https://mailauth-al6bxcngia-ue.a.run.app/mcp'
```

### Other

```json
{
  "mcpServers": {
    "theharrisontruong-web-mailauth-audit": {
      "type": "http",
      "url": "https://mailauth-al6bxcngia-ue.a.run.app/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-11-21 (score 73, +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.

### 2026-11-19 (score 72, +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-11-18 (score 71, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-17 (score 71)

First indexed and scored.

## MCP tools (2)

### `audit_mailauth` (~397 tokens)

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.

Input parameters:

- `domain` (string, required): Bare domain to audit, e.g. example.com

### `audit_mailauth_lite` (~142 tokens)

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.

Input parameters:

- `domain` (string, required): Bare domain to audit, e.g. example.com

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/theharrisontruong-web-mailauth-audit/mailauth-al6bxcngia-ue#diagnostics

## Score history

- 2026-11-21: 73
- 2026-11-20: 72
- 2026-11-19: 72
- 2026-11-18: 71
- 2026-11-17: 71

## Common questions

### 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.

## Links

- Remote endpoint: https://mailauth-al6bxcngia-ue.a.run.app/mcp
- Repository: https://github.com/theharrisontruong-web/agent-apis
- Website: https://mailauth-al6bxcngia-ue.a.run.app/
- Changelog RSS feed: https://verifymcp.io/servers/theharrisontruong-web-mailauth-audit/mailauth-al6bxcngia-ue.xml
- Changelog JSON feed: https://verifymcp.io/servers/theharrisontruong-web-mailauth-audit/mailauth-al6bxcngia-ue/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/theharrisontruong-web-mailauth-audit/mailauth-al6bxcngia-ue.json
- HTML version of this page: https://verifymcp.io/servers/theharrisontruong-web-mailauth-audit/mailauth-al6bxcngia-ue
