Email Validator for Agents
Related Servers
Alternatives to Email Validator for Agents
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceComprehensive email validation MCP server that checks syntax, MX records, disposable domains, role-based accounts, SPF/DKIM, typo suggestions, and risk scoring.MIT
- FlicenseNot gradedqualityDmaintenanceAn MCP server that provides email verification, bulk list cleaning, and signup risk assessment tools. It exposes three typed tools for agents: verify_email, clean_email_list, and assess_signup_risk, with real DNS MX checks and disposable domain detection.-
- FlicenseAqualityDmaintenanceAn MCP server that exposes a mock email verification tool over stdio transport, providing structured JSON results with statuses valid, invalid, or risky.1-
- FlicenseNot gradedqualityDmaintenanceMCP server that exposes an email verification tool, returning verdicts of valid, invalid, or risky with reasons.-
- AlicenseAqualityBmaintenanceAn MCP server that exposes a verify_email tool for checking email syntax, disposable domains, and MX records, returning a structured validity result.1ISC
- AlicenseBqualityDmaintenanceAn MCP server that provides email verification, returning valid, invalid, or risky status with detailed checks and metadata. It enables verifying email addresses via a simple tool interface.3MIT
TDQS
Scored across 2 tools
The two tools occupy clearly separated layers: check_email_syntax is a free, local, format-only check, while validate_emails is the paid network deliverability check. Each description explicitly states when to use the other instead, eliminating misselection risk.
Both names follow a consistent snake_case verb_noun pattern (validate_emails, check_email_syntax) with the subject ('emails') clearly identified. No mixed conventions or vague verbs.
Two tools is thin in absolute terms, but for a narrow email-validation purpose the free/paid split is a natural and justified decomposition rather than an under-built surface. Nothing appears to be padded or missing at the tool level.
The surface covers both the offline syntax tier and the full deliverability tier (syntax, DNS/MX, disposable, role, typo, SPF/DMARC) with documented verdicts and error rows. The only real gap is that mailbox existence/SMTP probing and any async run-status retrieval are absent, both explicitly acknowledged as out of scope.