VerifyAnyEmail MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VERIFYANYEMAIL_API_KEY | Yes | Your `vae_…` API key. Create one in the dashboard → API Keys. | |
| VERIFYANYEMAIL_BASE_URL | No | Override the API base URL. | https://api.verifyany.email |
| VERIFYANYEMAIL_TIMEOUT_MS | No | Per-request timeout in milliseconds. | 30000 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| verify_emailA | Verify whether a single email address is real and safe to send to, in real time. Returns a deliverability verdict (deliverable | undeliverable | risky | unknown), a 0–100 confidence score, a safeToSend flag, and signals (catch-all, disposable, role-based, free provider, likely typo). Spends 1 verification credit per call. Tip: addresses at the test.verifyany.email domain (e.g. deliverable@test.verifyany.email, undeliverable@…, risky@…, unknown@…) return canned results and cost 0 credits. |
| verify_batchA | Submit many email addresses for asynchronous bulk verification. Returns a batchId immediately; the job runs in the background. Poll get_batch_status until status is 'completed', then call get_batch_results. Reserves 1 credit per address. Prefer verify_email for one-off checks. |
| get_batch_statusA | Check the progress of a bulk verification batch: lifecycle state (queued | processing | completed | failed), addresses processed, and per-status counts once available. |
| get_batch_resultsA | Fetch a page of results for a bulk verification batch. Paginated — use page and pageSize for large batches. |
| check_mxA | Look up a domain's MX (mail exchanger) records and whether it can receive email. Free — no verification credits. |
| check_spfA | Check a domain's SPF record and flag common misconfigurations. Free — no verification credits. |
| check_dmarcA | Check a domain's DMARC policy (none | quarantine | reject) and alignment. Free — no verification credits. |
| check_dkimA | Check a domain's DKIM signing record for a given selector. Free — no verification credits. |
| check_domain_healthA | Run an overall email-deliverability health check for a domain — combines MX, SPF, DKIM, DMARC and related signals into a single graded summary with actionable findings. Free — no verification credits. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
The tools have clearly distinct purposes: single verification vs. batch submission vs. batch status/results, and individual DNS checks vs. an aggregate domain-health check. Descriptions clarify the relationship between check_domain_health and the individual check_* tools, preventing likely misselection.
Names follow predictable snake_case verb_noun patterns grouped by function: check_* for DNS diagnostics, verify_* for email verification, and get_batch_* for batch retrieval/status. The mixed prefix families are consistent within their domains and easy to infer.
Nine tools is well-scoped for an email verification and domain-health server. Each tool covers a meaningful operation, and there are no redundant or filler tools.
The core workflows are covered: single verification, batch submit/status/results, individual DNS checks, and aggregate domain health. Minor gaps exist around batch lifecycle management such as cancellation or listing batches, but these are not critical for typical agent use.