
Email Deliverability Audit API
Audit SPF, DKIM, DMARC, and MX for your sending domain and get a 0–100 deliverability score before you ship transactional email.
Overview
io.github.Br0ski777/email-deliverability is a MCP server for the Ship phase that audits SPF, DKIM, DMARC, and MX and returns a 0–100 email deliverability score.
What is this MCP server?
- Audits four pillars: SPF, DKIM, DMARC, and MX
- Returns a numeric deliverability score from 0 to 100
- Remote MCP over SSE at email-deliverability.api.klymax402.com
- x402 micropayment per audit call
- Version 1.1.0; GitHub repo email-deliverability-x402
- 4 email DNS/authentication areas audited: SPF, DKIM, DMARC, MX
- Deliverability score range: 0–100
- MCP server version 1.1.0
What problem does it solve?
You are about to ship app email but cannot tell if SPF, DKIM, DMARC, and MX are correct without manual checklists and scattered DNS tools.
Who is it for?
Indie SaaS founders validating transactional email DNS right before launch or after changing ESPs.
Skip if: High-volume senders who need inbox placement tests, IP reputation monitoring, or GDPR list-audit tooling in one product.
What do I get? / Deliverables
You get a scored deliverability audit in MCP so you can fix DNS policies before users see spam-folder password resets.
- SPF, DKIM, DMARC, and MX audit results
- Deliverability score on a 0–100 scale for gating ship decisions
Recommended MCP Servers
Journey fit
How it compares
Email authentication audit MCP, not a marketing automation skill or ESP dashboard.
Common Questions / FAQ
Who is io.github.Br0ski777/email-deliverability for?
Builders shipping transactional or product email who want agent-driven SPF, DKIM, DMARC, and MX validation with a simple score.
When should I use io.github.Br0ski777/email-deliverability?
Use it before go-live, after DNS changes, or when support reports mail going to spam due to authentication failures.
How do I add io.github.Br0ski777/email-deliverability to my agent?
Configure remote MCP SSE URL https://email-deliverability.api.klymax402.com/mcp and enable x402 micropayment in your MCP client.