Email Verification API

io.github.Br0ski777Published by GitHub account Br0ski777v1.2.0Updated Oct 24, 2026

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

VerifiedSSEWeb executableCommunication & CollaborationBusiness & Commerce

Overview

AI-generated overview

Remote MCP endpoint that verifies email addresses — syntax, MX, disposable and role flags, quality score — paid per call in USDC via x402.

What you can do
  • Verify a single email address and get a structured report with syntax, MX, disposable detection, role-based flags and a quality score from 0 to 100
  • Verify up to 100 addresses in one batch call, returning per-address results plus summary counts of valid, invalid and disposable entries
  • Use the results to clean lists, check CRM contacts or screen signups before outreach
When to use it
Useful when an assistant needs to check whether email addresses are deliverable before sending outreach, importing contacts into a CRM, or processing signups, and when bulk list cleaning of up to 100 addresses at a time is needed.
Requirements
A remote MCP endpoint; nothing to install locally. No signup or API key, but each call is paid in USDC on Base L2 through the x402 protocol, so an x402-capable client and a funded wallet are needed to complete the payment challenge. Network access to the provider's endpoint.
Before you install
Every call costs money: $0.005 per single verification and $0.03 per batch of up to 100, charged in USDC on Base through x402, so a wallet with funds is exposed to the service. Email addresses submitted are sent to a third-party API. The README also points to other paid APIs in the same marketplace, which are separate services.

Installation

In SourceWeft

  1. Open Email Verification 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-verification/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-verification-api": {
      "type": "sse",
      "url": "https://email-verification.api.klymax402.com/mcp"
    }
  }
}

README

Email Verification API

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

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

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

Quickstart -- HTTP (x402)

bash
curl -X POST "https://email-verification.api.klymax402.com/api/verify" \  -H "Content-Type: application/json" \  -d '{"email":"[email protected]"}'# -> 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. [email protected])

Example response:

json
{"valid":true,"syntax":true,"mx":true,"disposable":false,"role":false,"free":true,"score":85,"email":"[email protected]"}

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:

json
{"results":[{"email":"[email protected]","valid":true,"score":90},{"email":"[email protected]","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

Source: README.md at commit 3da5fce

Tools

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

Version history

1
  1. v1.2.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