Email Deliverability Audit API
Audit email domain deliverability: SPF, DKIM, DMARC, MX. Score 0-100. x402.
Installation
Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).
claude mcp add --transport sse email-deliverability-audit-api 'https://email-deliverability.api.klymax402.com/mcp'{
"mcpServers": {
"email-deliverability-audit-api": {
"type": "sse",
"url": "https://email-deliverability.api.klymax402.com/mcp"
}
}
}Documentation
Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.
Sommaire
Email Deliverability Audit API
Email deliverability audit for any domain. SPF, DKIM, DMARC, MX validation with score 0-100 and fix recommendations. Pay-per-call via x402 (USDC on Base L2) -- no API key, no signup, no rate-limit wall.
Part of the klymax402 marketplace -- 100 x402 micropayment APIs for AI agents, one wallet, USDC on Base.
Quickstart -- MCP
Add to your MCP client config (Claude Desktop, Cursor, ElizaOS, etc.):
{
"mcpServers": {
"email-deliverability": {
"url": "https://email-deliverability.api.klymax402.com/mcp"
}
}
}Quickstart -- HTTP (x402)
curl "https://email-deliverability.api.klymax402.com/api/audit?domain=..."
# -> 402 Payment Required, with an x402 payment challenge in the response bodyAny x402-aware client (@x402/fetch, x402-agent-tools, ATXP) handles the 402 -> sign -> retry cycle automatically.
Tools
| Tool | Method | Path | Price | Description |
|---|---|---|---|---|
email_audit_deliverability | GET | /api/audit | $0.012 | Audit email deliverability for a domain — checks SPF, DKIM, DMARC, MX records |
email_audit_deliverability | POST | /api/audit | $0.012 | Audit email deliverability for a domain — checks SPF, DKIM, DMARC, MX records (POST variant) |
email_audit_deliverability
Use this when you need to audit email deliverability configuration for a domain. Returns structured JSON with authentication record analysis and a deliverability score 0-100.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
domain | string | yes | Domain to audit (e.g. example.com, gmail.com) |
Example response:
{"score":65,"spf":{"found":true,"valid":true,"record":"v=spf1 include:_spf.google.com ~all"},"dkim":{"google":true,"default":false},"dmarc":{"found":true,"policy":"none","record":"v=DMARC1; p=none"},"mx":[{"priority":10,"exchange":"alt1.gmail-smtp-in.l.google.com"}],"recommendations":["Upgrade DMARC policy from none to quarantine","Add DKIM for default selector"]}When to use: launching email campaigns, onboarding new domains for outreach, or diagnosing inbox placement issues. Essential for email marketers, sales teams, and IT admins managing domain reputation.
Not for: single email validation (use email_verify_address), finding email addresses (use email_find_by_name), domain WHOIS/DNS (use domain_lookup_intelligence).
email_audit_deliverability
Use this when you need to audit email deliverability configuration for a domain. Returns structured JSON with authentication record analysis and a deliverability score 0-100. POST variant of email_audit_deliverability -- same params passed as JSON body instead of query string.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
domain | string | yes | Domain to audit (e.g. example.com, gmail.com) |
Example response:
{"score":65,"spf":{"found":true,"valid":true,"record":"v=spf1 include:_spf.google.com ~all"},"dkim":{"google":true,"default":false},"dmarc":{"found":true,"policy":"none","record":"v=DMARC1; p=none"},"mx":[{"priority":10,"exchange":"alt1.gmail-smtp-in.l.google.com"}],"recommendations":["Upgrade DMARC policy from none to quarantine","Add DKIM for default selector"]}When to use: launching email campaigns, onboarding new domains for outreach, or diagnosing inbox placement issues. Essential for email marketers, sales teams, and IT admins managing domain reputation.
Not for: single email validation (use email_verify_address), finding email addresses (use email_find_by_name), domain WHOIS/DNS (use domain_lookup_intelligence).
Example agent prompts
- "Audit email deliverability configuration for a domain"
- "Audit email deliverability configuration for a domain"
Payment
- Protocol: x402 -- HTTP-native pay-per-call, no signup, no API key
- Network: Base L2 (
eip155:8453) - Asset: USDC
- Facilitator: Coinbase CDP (primary), PayAI (fallback)
- Also reachable via ATXP (OAuth-wrapped x402, RFC 9728 protected-resource metadata)
Part of klymax402
100 x402 micropayment APIs for AI agents -- one wallet, USDC on Base, zero signup.
- Catalog: https://klymax402.com/llms.txt
- Full API reference: https://klymax402.com/llms-full.txt
- Live stats: https://klymax402.com/stats
License
MIT
Questions fréquentes
Qu'est-ce que Email Deliverability Audit API ?
Audit email domain deliverability: SPF, DKIM, DMARC, MX. Score 0-100. x402.
Comment installer Email Deliverability Audit API ?
Il fonctionne comme serveur distant. Dans Claude Code : claude mcp add --transport sse email-deliverability-audit-api 'https://email-deliverability.api.klymax402.com/mcp'. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.
Faut-il une clé API pour Email Deliverability Audit API ?
Son entrée au registre n'indique aucune clé ni secret obligatoire. Certaines fonctions peuvent tout de même demander un compte auprès du service auquel il se connecte.
Email Deliverability Audit API est-il open source ?
Oui. Son code est sur GitHub sous licence MIT.
Qui maintient Email Deliverability Audit API ?
Il est publié par Br0ski777. AI.tn le référence sans le maintenir ni le recommander.
Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.