contact-verification-mcp
Related Servers
Alternatives to contact-verification-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables agents to validate and normalize phone numbers, email addresses, and postal addresses with production-grade, country-specific rules, including formatting, typo detection, and checks for disposable domains or fictional numbers.31MIT
- AlicenseNot gradedqualityCmaintenanceEnables agents to validate email addresses and phone numbers before saving or using them, including syntax, DNS/MX checks, disposable domains, role addresses, typo suggestions, and phone number formats. Supports bulk email validation for up to 50 addresses in a single call.MIT

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- 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.-
- AlicenseAqualityBmaintenanceEnables AI assistants to verify single email addresses and bulk lists of up to 1,000 addresses in real time, checking RFC 5322 syntax, DNS MX records, disposable providers, role accounts, and typos, with an optional deep SMTP mailbox handshake. Bulk runs handle partial-quota situations gracefully.2MIT
- 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
TDQS
Scored across 4 tools
Each tool targets a distinct resource (address, email, phone) or a batch wrapper that explicitly replaces the single-record tools. The descriptions clearly differentiate purposes (e.g., email verification ≠ identity check).
All tool names follow the consistent pattern 'verify_' + a clear noun (postal_address, email, phone, batch). The convention is uniform and predictable.
Four tools cover the core verification operations (address, email, phone, plus a batch version). This is well-scoped and avoids unnecessary bloat or redundancy.
The tool surface covers the essential contact verification methods (postal, email, phone) and adds batch processing for efficiency. The descriptions explicitly disclaim unsupported features (e.g., phone line type, identity confirmation), making the scope clear with no obvious gaps.