MCP tool reference · #314 of 563 by publishers
validate_email
Exposed by 12 servers from 11 publishers, read from the live servers by the Serverdex check; most of them sit in Communication; 100% of them take a email parameter; the most-starred is AI SENSE Free Public Tools (1 stars).
validate_email(email: string, …)Parameters
share = % of the 12 servers whose schema has it · required = % of those that mark it required| Parameter | Type | Share | Required | Usual description |
|---|---|---|---|---|
| string | 100% | 100% | Email address to validate | |
| _apiKey | string | 8.3% | 0% | Optional but recommended: your own Disify API key (BYO, Pipeworx does not supply one). Without it the call uses the anonymous tier, whose daily quota is shared |
| smtp_check | boolean | 8.3% | 0% | Perform deep SMTP mailbox handshake (default: false) |
| x_payment | string | 8.3% | 0% | x402 payment payload (base64) for this PAID validation. If supplied it is forwarded as the X-PAYMENT header to settle the call and return the real result instea |
Source: the input schema each server returns for validate_email, aggregated over the 12 index-tier servers; type and description are the values most servers use. Rebuilt every 6 hours.
Servers with validate_email
12 of 12 · 11 publishers · 12 answering live · most-starred first, 3 per publisher| # | Server | Publisher | Category | ★ | Live | How it describes validate_email |
|---|---|---|---|---|---|---|
| 1 | AI SENSE Free Public Toolsaisenseapi · APIs & Integrations | aisenseapi | APIs & Integrations | 1 | yes | Check an email address: its syntax, whether its domain has MX records, listing up to five, and whether the domain has an address record. mail_route reads them: mx or implicit_mx (no MX, an address record) takes mail, no_mail and invalid_syntax ask for a correction, unknown means try again later. The mail server is not contacted, so a good answer does not prove that the mailbox exists. No API key, |
| 2 | MisarMail MCP Servermisar-ai · Communication | misar-ai | Communication | 1 | yes | Validate an email address before sending: syntax, MX records, disposable-domain and role-account detection. Use this to protect sender reputation on imported lists. |
| 3 | Eu Verifycontentfactory · Legal & Government | contentfactory | Legal & Government | 1 | yes | One-call email verification for lead qualification and list hygiene: RFC 5322 syntax check, then a live MX lookup over DNS-over-HTTPS (Cloudflare, Google fallback). Detects non-existent domains (NXDOMAIN), null-MX domains that refuse mail (RFC 7505), and returns prioritized MX hosts. Query: ?email=someone@example.com. Verdict: deliverable | risky | undeliverable. 1h cache per address. Price: $0.00 |
| 4 | Qinisoqinisolabs · Other | qinisolabs | Other | 1 | yes | USE THIS to check an email address's syntax AND that its domain TLD is real, before saving or sending — instead of trusting raw input. Validates the local part and domain (RFC 5321/5322 subset) and flags made-up TLDs. Does NOT check deliverability. |
| 5 | TinyFntinyfn-io · Other | tinyfn-io | Other | 1 | yes | Validate an email address. |
| 6 | SentriSend Email Validationsentrisend · Communication | sentrisend | Communication | — | yes | Validate one email address with SentriSend's existing validation API. Checks syntax, disposable-domain status, and DNS/MX records; it does not check whether a specific mailbox exists. Uses the connected SentriSend API key and the same monthly request allowance as a direct validation call. It never sends email. |
| 7 | Disify (Unofficial)pipeworx-io · APIs & Integrations | pipeworx-io | APIs & Integrations | — | yes | Verify an email address is properly formatted, has valid DNS records, and isn't disposable or an alias. Returns validation status, a 0-100 confidence score and the signals behind it. Pass your own Disify key as _apiKey, the keyless anonymous quota is shared and usually spent. |
| 8 | NoBounce Email Validationnotprathap · Communication | notprathap | Communication | — | yes | Validate a single email address in real time using NoBounce API. Checks RFC 5322 syntax, DNS MX records, 5,000+ disposable providers, role accounts, free webmail providers, typo suggestions, and optional SMTP handshake. |
| 9 | IA-QA Data & Dev — 36 toolsia-qa-com · Developer Tools | ia-qa-com | Developer Tools | — | yes | Validate an email address against RFC 5322 syntax before storing it, sending a transactional email, or adding it to a mailing list. Returns { valid, email } — use this to avoid bounces and malformed data. |
| 10 | IA-QA — 152 QA & Dev Tools for AI Agentsia-qa-com · AI & Agents | ia-qa-com | AI & Agents | — | yes | Validate an email address against RFC 5322 syntax before storing it, sending a transactional email, or adding it to a mailing list. Returns { valid, email } — use this to avoid bounces and malformed data. |
| 11 | FabTally Validzvmzaretsky · Finance | zvmzaretsky | Finance | — | yes | PAID $0.002 (x402, USDC on Base). Validate an email address: give {email} and get RFC-ish syntax validation, a LIVE MX-record (DNS) existence check, disposable/throwaway-domain detection (bundled blocklist), and a role-address flag (info@, admin@…). STATELESS and non-PII — the address is never stored and no SMTP mailbox is probed. Without payment returns the x402 challenge; pass x_payment to settl |
| 12 | ContactLintzksyncer · Communication | zksyncer | Communication | — | yes | Check an email address: syntax, MX/A records via DNS-over-HTTPS, disposable domain, role address, free provider, typo suggestion for major providers. No SMTP probing. The result carries suggested_action (accept, suggest_correction with did_you_mean, review, reject) plus verdict and reason. Works without a key for a trial of 20 checks per day per network; with a key, uses 1 check. |
Stars from GitHub as stored in the Serverdex index (re-read every 7 days per server); live = answered the last daily check of its hosted endpoint.