Email Verification API
Let an agent validate waitlist and signup emails for syntax, MX, disposables, and a 0–100 quality score before you accept leads on a landing page.
Overview
io.github.Br0ski777/email-verification is a MCP server for the Validate phase that checks email syntax, MX, disposables, and a 0–100 quality score over remote SSE with x402 USDC payment.
What is this MCP server?
- Checks syntax, MX records, and disposable-email detection
- Returns a quality score from 0 to 100 for each address
- Remote SSE MCP at email-verification.api.klymax402.com
- x402 USDC micropayment per verification call
- Manifest version 1.2.0 on MCP server schema 2025-12-11
- Quality score range 0–100 per server description
- 1 remote SSE endpoint: email-verification.api.klymax402.com/mcp
What problem does it solve?
Fake and low-quality emails on your landing page silently waste onboarding email and distort validation metrics.
Who is it for?
Solo builders testing waitlists, betas, or pricing pages who want agent-driven verification without integrating a separate email hygiene API first.
Skip if: Builders who only need client-side format checks or who already run a full marketing automation suite with built-in list cleaning.
What do I get? / Deliverables
Your agent can reject or flag risky addresses at capture time using structured verification and a numeric quality score.
- Per-address verification result with syntax, MX, and disposable signals
- Numeric quality score from 0 to 100 for funnel decisions
Recommended MCP Servers
Journey fit
Email verification belongs in validate because it hardens lead capture and signup flows before you scale acquisition spend. Landing subphase covers forms, waitlists, and early user capture where bad addresses waste follow-up and hurt sender reputation.
How it compares
Pay-per-call verification MCP over SSE, not a CRM plugin or deliverability consulting skill.
Common Questions / FAQ
Who is io.github.Br0ski777/email-verification for?
Indie builders and small teams validating signups on landing pages who want MCP-accessible email quality checks before scaling outreach.
When should I use io.github.Br0ski777/email-verification?
Use it during validate when you are collecting emails on a prototype or landing page and need MX, disposable, and score-based filtering before nurture sequences.
How do I add io.github.Br0ski777/email-verification to my agent?
Add remote MCP SSE URL https://email-verification.api.klymax402.com/mcp in your agent config, set up x402 USDC payment, then invoke verification tools on addresses your agent collects or parses.