Email Verifier MCP
Related Servers
Alternatives to Email Verifier MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables an AI agent to verify a single email address in real time, clean an entire uploaded list file with per-address verdicts, and download the results as CSV with the addresses that are safe to send to. It runs on npm with zero dependencies and includes built-in credit reporting and spending limits so agents cannot overspend without approval.367 npmMIT
- AlicenseNot gradedqualityCmaintenanceReal-time email verification API with syntax, MX, disposable detection, role-based flags, quality score 0-100. Built for agent outreach pipelines with pay-per-call via x402 (USDC on Base L2) -- no API key, no signup, no rate-limit wall.MIT
- FlicenseNot gradedqualityBmaintenanceEnables AI agents to verify email addresses in real-time, checking syntax, DNS, MX records, and SMTP handshake, returning verdicts and deliverability scores without sending actual emails.-
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to assess cold-email deliverability by checking sending domains' SPF/DKIM/DMARC/MX configuration and scanning subject/body copy for spam-triggering patterns, with scores and risk levels. Runs locally over stdio without SaaS signup or API keys.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to check an email address for syntax validity, MX records, disposable/role/free-provider flags, and a deliverability score/verdict, with per-call USDC payment on Base.MIT
- AlicenseNot gradedqualityBmaintenanceKeyless email validation: disposable/burner, role-account, and free-provider detection, MX checks, and typo suggestions. Tools: check_email, check_domain.MIT
TDQS
Scored across 4 tools
check_email is a superset that already performs MX, syntax, and disposable checks, so is_disposable and check_mx overlap with it. However, the boundaries are readable: the standalone tools are lightweight single-purpose checks while check_email is the comprehensive one, and verify_bulk is clearly the batch variant.
The set mixes a predicate style (is_disposable), a check_ verb (check_email, check_mx), and a verify_ verb (verify_bulk), where 'check' and 'verify' are synonyms used inconsistently. All snake_case and readable, but the verb conventions are not unified.
Four tightly-scoped tools is well-suited to a focused email-verification server, with each tool earning its place (single checks, full check, bulk, MX lookup). No bloat or thinness.
Covers syntax, MX, disposable, role accounts, and bulk verification, which is strong lifecycle coverage for the domain. Minor gaps: no standalone role-account or catch-all detection tool, and SMTP is opt-in only, but these are deliberate and workable.