Email Deliverability Audit API

io.github.Br0ski777Published by GitHub account Br0ski777v1.1.0Updated Oct 25, 2026

Audit email domain deliverability: SPF, DKIM, DMARC, MX. Score 0-100. x402.

The publisher's own server: audit.domains - Domain Valuation

Overview

AI-generated overview

Remote MCP endpoint that audits a domain's email deliverability (SPF, DKIM, DMARC, MX) and returns a 0-100 score with fix recommendations.

What you can do
Audit a domain's email authentication setup, checking SPF, DKIM, DMARC and MX records and returning structured JSON with a deliverability score from 0 to 100 and fix recommendations. The same audit is offered as a GET and a POST variant, both taking a domain parameter.
When to use it
Useful when launching email campaigns, onboarding new domains for outreach, or diagnosing inbox placement problems and domain reputation. It is not for single-address validation, address discovery or general WHOIS/DNS lookups.
Requirements
A remote MCP endpoint reached over SSE; no API key or signup. Each call is paid per request via x402 in USDC on Base L2, so an x402-aware client with a funded wallet is needed to complete the payment challenge.
Before you install
Every audit call costs money ($0.012 per call in USDC on Base), so automated or repeated calls can spend from the connected wallet. Payment is handled through third-party facilitators (Coinbase CDP, PayAI), and the audited domain is sent to the remote service.

Installation

In SourceWeft

  1. Open Email Deliverability Audit API in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via SSE. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.Br0ski777%2Femail-deliverability/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "email-deliverability-audit-api": {
      "type": "sse",
      "url": "https://email-deliverability.api.klymax402.com/mcp"
    }
  }
}

README

Email Deliverability Audit API

[MCP Server] [x402] [License: MIT]

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.):

json
{  "mcpServers": {    "email-deliverability": {      "url": "https://email-deliverability.api.klymax402.com/mcp"    }  }}

Quickstart -- HTTP (x402)

bash
curl "https://email-deliverability.api.klymax402.com/api/audit?domain=..."# -> 402 Payment Required, with an x402 payment challenge in the response body

Any x402-aware client (@x402/fetch, x402-agent-tools, ATXP) handles the 402 -> sign -> retry cycle automatically.

Tools

ToolMethodPathPriceDescription
email_audit_deliverabilityGET/api/audit$0.012Audit email deliverability for a domain — checks SPF, DKIM, DMARC, MX records
email_audit_deliverabilityPOST/api/audit$0.012Audit 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

NameTypeRequiredDescription
domainstringyesDomain to audit (e.g. example.com, gmail.com)

Example response:

json
{"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

NameTypeRequiredDescription
domainstringyesDomain to audit (e.g. example.com, gmail.com)

Example response:

json
{"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.

License

MIT

Source: README.md at commit adc4c9b

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.1.0LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Audit integrations