Email Verifier MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APIFY_TOKEN | No | Your Apify token, used as a Bearer token in the Authorization header when connecting to the hosted Apify endpoint (https://neeenja--email-verifier-mcp.apify.actor/mcp). Not required when running locally via npx. |
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
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_emailA | DNS-based email verification: RFC 5321 syntax, MX record lookup, disposable + role-account detection. SMTP handshake is OPT-IN and off by default (compliance). Returns both a human summary and structured data. |
| verify_bulkB | Batch verification of up to 10 emails. Same DNS-based checks as check_email. Returns a per-email array plus a summary. |
| check_mxA | Standalone DNS MX-record lookup. Returns the mail-exchanger list sorted by priority. |
| is_disposableB | Detects throwaway / temporary email providers using a ~160k-domain MIT blacklist (auto-refreshed weekly). Accepts a full email or a bare domain. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| verify_signup_email | Guide an agent to verify a signup email and make an accept / flag / reject decision. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| blacklist-stats | Size and source of the loaded disposable-domain blacklist. |
TDQS
Scored across 4 tools
check_email is a superset that already performs MX, syntax, and disposable checks, so is_disposable and check_mx overlap with it. However, the boundaries are readable: the standalone tools are lightweight single-purpose checks while check_email is the comprehensive one, and verify_bulk is clearly the batch variant.
The set mixes a predicate style (is_disposable), a check_ verb (check_email, check_mx), and a verify_ verb (verify_bulk), where 'check' and 'verify' are synonyms used inconsistently. All snake_case and readable, but the verb conventions are not unified.
Four tightly-scoped tools is well-suited to a focused email-verification server, with each tool earning its place (single checks, full check, bulk, MX lookup). No bloat or thinness.
Covers syntax, MX, disposable, role accounts, and bulk verification, which is strong lifecycle coverage for the domain. Minor gaps: no standalone role-account or catch-all detection tool, and SMTP is opt-in only, but these are deliberate and workable.