Email Deliverability Audit API
Email Deliverability Audit API is an MCP server published by Br0ski777, verified on MCP revision 2024-11-05; support for the current revision (2026-07-28) is not yet confirmed. Last verified 2026-08-25.
Does Email Deliverability Audit API support the current MCP specification (2026-07-28)?
Not yet confirmed. Email Deliverability Audit API is verified on revision 2024-11-05; we have not confirmed support for the current revision (2026-07-28) as of 2026-08-25.
Is Email Deliverability Audit API a first-party (official) MCP server?
Undetermined. We have not verified the publisher relationship for Email Deliverability Audit API (as of 2026-08-25).
How do I connect to Email Deliverability Audit API?
Email Deliverability Audit API is available via a hosted remote endpoint at https://email-deliverability.api.klymax402.com/mcp, the official MCP Registry under io.github.Br0ski777/email-deliverability, the source repository at https://github.com/br0ski777/email-deliverability-x402. Authentication: none. Transports: streamable-http.
What tools does Email Deliverability Audit API expose?
Email Deliverability Audit API exposes 2 tools, including email_audit_deliverability, email_audit_deliverability (last verified 2026-08-25).
Does Email Deliverability Audit API support MCP revision 2024-11-05?
Yes. Email Deliverability Audit API supports MCP revision 2024-11-05 (checked 2026-08-25).
When were Email Deliverability Audit API's facts last verified?
2026-08-25. Each fact on this page links to the sources used to verify it.
Which tools does Email Deliverability Audit API expose?
2 tools verified.
email_audit_deliverabilityemail_audit_deliverability
Audit email domain deliverability: SPF, DKIM, DMARC, MX. Score 0-100. x402.
Which MCP spec revisions does Email Deliverability Audit API support?
Email Deliverability Audit API has 1 verified spec-support record. Each row lists the revision, the verified status, the evidence URL, and the date that fact was last checked.
| Spec revision | Status | Last checked | Evidence |
|---|---|---|---|
| MCP 2024-11-05 | Supported | Source |
How widely adopted is Email Deliverability Audit API?
Ranked #319 in The MCP 500 with Adoption Index 48.50 (snapshot , methodology v1).
| Measurement | Value | Source |
|---|---|---|
| Official MCP Registry | yes | API · |
| Docker MCP Catalog | no | API · |
| Smithery uses | 3,838 | API · |
| GitHub stars | 0 | API · |
| GitHub forks | 0 | API · |
| Last push | 2026-09-02T19:55:47Z | API · |
| Repository archived | no | API · |
Repository and package signals for Email Deliverability Audit API
Measured directly from the source registries, not asserted from a document. Each figure carries the date it was read; none of it affects the verified spec status above.
Repository as of
- Created
- Open issues
- 0
- Primary language
- TypeScript
- License (repository)
- MIT
- Continuous integration
- None detected
- Tests
- None detected
- Security policy
- None
Declared topics: ai-agents, mcp, mcp-server, monitoring, security, x402 — author-declared on the repository, not our taxonomy.
How was this verified, and what are the sources?
Verified · method: endpoint-probe
· confidence 0.85 (Good).
- Official MCP Registry record for io.github.Br0ski777/email-deliverability at version 1.1.0 - lists remote endpoint https://email-deliverability.api.klymax402.com/mcp and repository https://github.com/br0ski777/email-deliverability-x402 - accessed
- Endpoint probe of https://email-deliverability.api.klymax402.com/mcp - declined server/discover; negotiated 2024-11-05 via the legacy initialize handshake; tools/list returned 2 tools - accessed
- Endpoint probe of https://email-deliverability.api.klymax402.com/mcp - declined server/discover; negotiated 2024-11-05 via the legacy initialize handshake; tools/list returned 2 tools - accessed