Email Verifier MCP Server
Related Servers
Alternatives to Email Verifier MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables checking lead rows, CSV files, or Apify datasets for duplicates, email syntax and risk signals, domain issues, missing fields, and stale dates, returning a per-row import, review, or reject verdict so only clean records reach a CRM or sequencer.172 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables autonomous AI agents and LLM toolchains to verify email deliverability in batches through Verifalia, with deduplication, Redis-backed zero-credit cache recovery, and daily quota protection.MIT
- 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.15 npmMIT
- 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 agents to verify an email list before sending, returning a pass/fail plus keep, remove, and review categories with reasons. It exposes check_emails and check_file tools over stdio, with optional Analyzemail mailbox verification.195 npm2MIT
- AlicenseNot gradedqualityBmaintenanceEnables local, self-hosted email verification with syntax and DNS/MX checks, disposable-address detection, and bounded bulk CSV processing without paid API dependencies.GPL 3.0
TDQS
Scored across 1 tool
There is only one tool, so there is no possibility of misselection or overlap. Its purpose (batch-verify email addresses via a chosen provider) is unambiguous and fully described.
The single tool follows a clear snake_case verb_noun pattern (verify_emails), which matches the naming conventions an agent would expect. There is no mixing of conventions to penalize.
A single batch tool (1 to 5,000 addresses) is a sensible, well-scoped surface for a narrow email-verification service. It is slightly thin in that there is no separate lightweight single-address or account-info entry point, but nothing is redundant.
The core operation—verifying addresses and returning rich per-row verdicts—is fully covered, and input validation, deduplication, and error reporting are handled within the tool. Minor gaps exist: no way to check provider account credits/API key validity or list supported providers before spending money, which agents can only work around by trial.