Email Verifier
Server Details
Verify emails: syntax, MX, disposable, role, typo fix, optional SMTP probe, SPF/DMARC.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 5 tools
Each tool targets a distinct operation: domain-level checks, text extraction, typo correction, single verification, and batch verification. The only real overlap is between domain_check and verify_email, which also performs MX/domain checks internally, but the descriptions make the scope difference (domain vs. address) clear enough to choose correctly.
All five tools use a consistent snake_case verb_noun pattern (domain_check, extract_emails, suggest_fix, verify_email, verify_emails). The singular/plural pairing of verify_email and verify_emails is a predictable, readable convention.
Five tools is well-scoped for an email verification service, and each one earns its place: extraction, typo fixing, single verify, batch verify, and domain inspection. There is no filler or redundancy beyond the intentional single/batch pair.
The surface covers the full verification lifecycle: extract addresses, clean typos, verify one, verify many, and inspect a domain. Minor gaps exist around account/quota visibility (this is a paid, per-address-charged API) and no async job handling for very large batches, but agents can work around both.
Available Tools
5 toolsdomain_checkCheck a domain's mail setupARead-onlyIdempotentInspect
Does the domain accept mail, which MX hosts, is it a disposable or free-mail provider, does it publish SPF and DMARC (and the DMARC policy)? Use before trusting a sender domain or when onboarding a company. Example: domain 'noahsarch.tech'. Response: result with status (deliverable | risky | undeliverable | invalid | unknown), reason, score 0–100, the checks run, plus data_confidence, estimated_items[], sources[], data_version, warnings[] and a disclaimer. No logging of addresses.
Inputs: domain (required). Returns: object
extract_emailsPull email addresses out of textARead-onlyIdempotentInspect
Find every address in a block of text or HTML (deduped by default). Free. Pair with verify_emails. Response: result with status (deliverable | risky | undeliverable | invalid | unknown), reason, score 0–100, the checks run, plus data_confidence, estimated_items[], sources[], data_version, warnings[] and a disclaimer. No logging of addresses.
Inputs: text (required), dedupe. Returns: object
suggest_fixSuggest a correction for a mistyped addressARead-onlyIdempotentInspect
Fix common typos: gmial.com, hotmail.con, yaho.com, stray spaces/dots. Returns the suggestion (or null) and which fixes applied. Free. Example: email 'sara@gmial.con'. Response: result with status (deliverable | risky | undeliverable | invalid | unknown), reason, score 0–100, the checks run, plus data_confidence, estimated_items[], sources[], data_version, warnings[] and a disclaimer. No logging of addresses.
Inputs: email (required). Returns: object
verify_emailVerify one email addressARead-onlyIdempotentInspect
Full check of one address: RFC syntax and normalisation, domain existence and MX records (incl. null-MX and implicit-MX), disposable-provider list (10k+ domains), role account, free-mail provider, typo suggestion; optional SMTP RCPT probe with catch-all detection and optional SPF/DMARC. Example: email 'john.doe@gmail.com', smtp_check false. Response: result with status (deliverable | risky | undeliverable | invalid | unknown), reason, score 0–100, the checks run, plus data_confidence, estimated_items[], sources[], data_version, warnings[] and a disclaimer. No logging of addresses.
Inputs: email (required), smtp_check, check_policy. Returns: object
verify_emailsVerify up to 1,000 emails in one callARead-onlyIdempotentInspect
Same checks as verify_email for a list, run in parallel with per-domain DNS caching; returns per-address results, a summary by status, and clean (the deliverable ones). Charged per unique address. Example: emails ['a@x.com','b@y.org'], smtp_check false. Response: result with status (deliverable | risky | undeliverable | invalid | unknown), reason, score 0–100, the checks run, plus data_confidence, estimated_items[], sources[], data_version, warnings[] and a disclaimer. No logging of addresses.
Inputs: emails (required), dedupe, smtp_check, check_policy. Returns: object
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Verify email addresses: syntax, MX, disposable, role, SMTP mailbox, catch-all and typo checks.
Validate emails without sending mail: syntax, MX, disposable, role and typo checks, SPF/DMARC.
Verify emails: syntax, MX, SMTP mailbox, disposable, role and catch-all checks. Single and bulk.
Verify emails — deliverability, disposable/role/free detection, MX validity, domain age.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceProvides email verification as a tool, performing syntax validation, domain verification, and disposable-domain risk detection.-
- 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 gradedqualityBmaintenanceKeyless email validation: disposable/burner, role-account, and free-provider detection, MX checks, and typo suggestions. Tools: check_email, check_domain.MIT
- AlicenseNot gradedqualityDmaintenanceProvides email verification as an MCP tool, checking format, disposable domains, and mail server availability with structured results.ISC
Glama MCP Gateway
Add one secure layer between your agents and this server.