Email Verifier MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APIFY_TOKEN | Yes | Your Apify API token from console.apify.com/account/integrations. Required for tool calls. | |
| EMAIL_VERIFIER_API_KEY | Yes | Your API key for ZeroBounce, NeverBounce, MillionVerifier, BounceBan, or Reoon Email Verifier. |
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_emailsA | Check whether email addresses will deliver, using the caller's own ZeroBounce, NeverBounce, MillionVerifier, BounceBan, or Reoon account. Give emails (1 to 5,000 addresses) and provider (zerobounce by default). The service API key is read from this server's environment (EMAIL_VERIFIER_API_KEY), never from the tool arguments, and the service bills each check to the key owner. Returns one flat row per address: verdict (valid, invalid, catch_all, risky, or unknown), provider_status, provider_sub_status, is_role, is_free_email, is_disposable, did_you_mean, row_status, and error_reason. Addresses with broken syntax are not sent; repeats are checked once. If the key is missing the call is refused before any run starts. Bad input returns one free row whose error_reason starts with input_invalid. A run that does not succeed is returned as an error with its run ID. Read-only; requires an APIFY_TOKEN; Apify charges per address the service answered valid, invalid, catch all, or risky. |
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 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.