Email Verification API

Registre officiel Productivité

Verify emails: syntax, MX records, disposable detection, quality score 0-100. x402 USDC.

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

Remote (sse)
Claude Code
claude mcp add --transport sse email-verification-api 'https://email-verification.api.klymax402.com/mcp'
Configuration JSON (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "email-verification-api": {
            "type": "sse",
            "url": "https://email-verification.api.klymax402.com/mcp"
        }
    }
}

Documentation

Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.

Sommaire
  1. Email Verification API
  2. Quickstart -- MCP
  3. Quickstart -- HTTP (x402)
  4. Tools
  5. Example agent prompts
  6. Payment
  7. Part of klymax402
  8. License

Email Verification API

Real-time email verification API. Syntax, MX, disposable detection, role-based flags, quality score 0-100. Built for agent outreach pipelines. 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-verification": {
      "url": "https://email-verification.api.klymax402.com/mcp"
    }
  }
}

Quickstart -- HTTP (x402)

curl -X POST "https://email-verification.api.klymax402.com/api/verify" \
  -H "Content-Type: application/json" \
  -d '{"email":"user@example.com"}'
# -> 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_verify_addressPOST/api/verify$0.005Verify a single email address
email_verify_batchPOST/api/verify/batch$0.03Verify up to 100 email addresses in batch
email_verify_address

Verify email deliverability in real-time. Alternative to Hunter email-verifier at 15x lower cost. Returns a structured JSON report with syntax, MX, disposable detection, role-based flags, and quality score 0-100.

Parameters

NameTypeRequiredDescription
emailstringyesEmail address to verify (e.g. user@example.com)

Example response:

{"valid":true,"syntax":true,"mx":true,"disposable":false,"role":false,"free":true,"score":85,"email":"john@gmail.com"}

When to use: sending outreach emails, adding contacts to CRM, or processing signups. Essential for verifying email deliverability, cleaning email lists, detecting fake registrations, and qualifying leads. Drop-in replacement for Hunter email verification.

Not for: finding emails (use email_find_by_name), person data (use person_enrich_from_email), domain deliverability audit (SPF/DKIM/DMARC) (use email_audit_deliverability).

email_verify_batch

Use this when you need to validate multiple email addresses at once (up to 100). Returns a JSON array of verification results plus summary counts.

Parameters

NameTypeRequiredDescription
emailsarrayyesArray of email addresses (max 100)

Example response:

{"results":[{"email":"a@test.com","valid":true,"score":90},{"email":"b@mailinator.com","valid":false,"score":10}],"summary":{"total":2,"valid":1,"invalid":1,"disposable":1}}

When to use: bulk list cleaning, CRM hygiene, or pre-campaign validation. Essential when you have 5+ emails to verify at once.

Not for: single emails (use email_verify_address), finding emails (use email_find_by_name).

Example agent prompts

  • "Verify email deliverability in real-time"
  • "Validate multiple email addresses at once (up to 100)"

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

Questions fréquentes

Qu'est-ce que Email Verification API ?

Verify emails: syntax, MX records, disposable detection, quality score 0-100. x402 USDC.

Comment installer Email Verification API ?

Il fonctionne comme serveur distant. Dans Claude Code : claude mcp add --transport sse email-verification-api 'https://email-verification.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 Verification 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 Verification API est-il open source ?

Oui. Son code est sur GitHub sous licence MIT.

Qui maintient Email Verification 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.