Server data from the Official MCP Registry
Verify emails: syntax, MX records, disposable detection, quality score 0-100. x402 USDC.
Verify emails: syntax, MX records, disposable detection, quality score 0-100. x402 USDC.
Remote endpoints: sse: https://email-verification.api.klymax402.com/mcp
This MCP server implements email verification with payment gating via x402 and ATXP protocols. Critical security issues include hardcoded cryptocurrency wallet address and API credentials exposed in source code, missing input validation on email parameters, and reliance on external payment middleware with unclear security posture. The server performs DNS lookups on user-supplied domains without rate limiting or SSRF protections, creating potential for abuse. Supply chain analysis found 8 known vulnerabilities in dependencies (0 critical, 3 high severity).
6 files analyzed · 21 issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
This plugin requests these system permissions. Most are normal for its category.
Unverified package source
We couldn't verify that the installable package matches the reviewed source code. Proceed with caution.
Available as Local & Remote
This plugin can run on your machine or connect to a hosted endpoint. during install.
From the project's GitHub README.
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.
Add to your MCP client config (Claude Desktop, Cursor, ElizaOS, etc.):
{
"mcpServers": {
"email-verification": {
"url": "https://email-verification.api.klymax402.com/mcp"
}
}
}
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.
| Tool | Method | Path | Price | Description |
|---|---|---|---|---|
email_verify_address | POST | /api/verify | $0.002 | Verify a single email address |
email_verify_batch | POST | /api/verify/batch | $0.015 | Verify up to 100 email addresses in batch |
email_verify_addressVerify 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
| Name | Type | Required | Description |
|---|---|---|---|
email | string | yes | Email 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_batchUse 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
| Name | Type | Required | Description |
|---|---|---|---|
emails | array | yes | Array 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).
eip155:8453)100 x402 micropayment APIs for AI agents -- one wallet, USDC on Base, zero signup.
MIT
Be the first to review this server!
by Modelcontextprotocol · Developer Tools
Web content fetching and conversion for efficient LLM usage
by Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
by mcp-marketplace · Developer Tools
Create, build, and publish Python MCP servers to PyPI — conversationally.