ezverify-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOST | No | HTTP mode bind host. Defaults to 127.0.0.1 when not set. | |
| PORT | No | Set this to run the MCP server as an HTTP service instead of stdio, e.g. PORT=3100. | |
| EZVERIFY_API_KEY | No | Your EzVerify API key. Required for the default stdio mode. Not used in HTTP mode. |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| verify_emailA | Verify a single email address. Returns status (valid/invalid/risky/unknown), deliverability score, syntax/domain/MX/SMTP flags, disposable domain detection, role account flag, typo suggestion, and mailbox-full status. Uses credits: 1 credit for a definitive result (valid, invalid or risky); unknown results are free. Checking the same address again is charged again. |
| verify_emails_bulkA | Submit an async bulk email verification job (up to 1,000 emails per request; duplicate addresses are verified and billed once). Returns a request_id — poll with get_bulk_job_status. Uses credits: 1 credit per address with a definitive result (valid, invalid or risky), charged when the job completes; unknown results are free. |
| get_bulk_job_statusA | Check the status of a bulk verification job. Returns progress, counts, and full results when completed. Free: does not use credits. |
| get_usage_statsA | Get EzVerify request statistics for the last N days: total requests, credits used, valid/invalid/risky/unknown counts, average processing time. Covers single verifications (API or dashboard Quick Verify) plus one entry per bulk submission; credits and per-address results of bulk jobs are NOT included — use get_account_info for this month's credit total. Free: does not use credits. |
| get_account_infoA | Get EzVerify account info: current plan, credits used this calendar month, credits remaining, monthly credit limit. Credits reset on the 1st of each month; usage beyond the limit is billed as overage. Free: does not use 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 5 tools
Each tool has a clearly distinct purpose: single verification, bulk submission, bulk status polling, historical usage stats, and account/credit information. The descriptions explicitly clarify the boundary between get_usage_stats and get_account_info, avoiding likely confusion.
All tool names use consistent snake_case with an action-oriented verb and clear noun phrase (verify_email, verify_emails_bulk, get_bulk_job_status, get_usage_stats, get_account_info). The pattern is predictable throughout.
Five tools are well-scoped for an email verification service, covering both single and bulk workflows plus account and usage visibility. No tool feels redundant or excessive.
The surface covers the core lifecycle: single verification, bulk job submission, bulk job status retrieval, usage reporting, and account/credit information. No obvious operational dead end is present for the stated purpose.