NoBounce Email Validation MCP Server
Related Servers
Alternatives to NoBounce Email Validation MCP Server
No user-submitted related servers found.
Related Servers
- 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.-

Mailveri MCP Serverofficial
AlicenseAqualityCmaintenanceEnables AI assistants to verify email deliverability and check mailbox existence, manage bulk verification batches, and monitor verification credit balances directly from chat.61MIT- AlicenseAqualityDmaintenanceProvides email validation and domain configuration auditing tools for AI assistants, enabling single address checks, bulk list cleaning, SPF verification, and full mail setup grading (A-F) with actionable fixes.441 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to verify email addresses through a multi-signal probabilistic pipeline, returning confidence scores and honest statuses (safe/risky/invalid/unknown) with evidence.Apache 2.0
- AlicenseAqualityAmaintenanceEnables AI agents to verify email addresses and receive a 'send', 'hold', or 'kill' verdict with the reason, while also managing signup and credits programmatically.52MIT
- AlicenseAqualityDmaintenanceEnables AI assistants to verify email deliverability and find business emails via the Verifox API, supporting single and bulk operations.655 npmMIT
TDQS
Scored across 2 tools
The two tools are cleanly separated by scope: validate_email handles one address, validate_emails_bulk handles batches up to 1,000. There is no realistic scenario where an agent could confuse the two, and the naming itself signals the distinction.
Both tools use snake_case with the same validate_ verb and the same email/emails noun stem, giving a predictable pattern. The only minor deviation is the plural-plus-'bulk' qualifier on the batch variant, which is still readable and conventional.
Two tools is on the thin side even for a narrow validation service; it is essentially one operation exposed in single and bulk form. The count is defensible for the scope but leaves little surface for account/quota management.
Single and bulk validation cover the core domain (syntax, MX, disposable, role, free, typo, SMTP) well. The notable gap is the absence of any quota/credits or account-status tool, despite bulk mentioning 'partial-quota handling' — agents cannot inspect remaining quota before large batches.