ezverify-mcp
EzVerify MCP lets you verify email addresses and check your EzVerify account through an MCP client.
Verify a single email and get status, deliverability score, syntax/domain/MX/SMTP flags, disposable-domain, role-account, typo, and mailbox-full details (uses credits).
Submit bulk verification jobs of up to 1,000 emails and poll job status/results (uses credits; duplicates billed once).
Get request statistics over the last N days (free; excludes bulk-job credits/per-address results).
Get your current plan, monthly credits used, remaining credits, and monthly limit (free).
Use it with Claude Desktop, Claude Code, or other stdio MCP clients, or self-host it in HTTP mode.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@ezverify-mcp verify sarah.jones@acme.com for me"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
ezverify-mcp: requires an EzVerify Starter or Business plan
Requires an EzVerify Starter or Business plan. The Free plan is web-app only: its API key is rejected with 403 plan_upgrade_required.
EzVerify MCP server: lets an MCP client such as Claude verify email addresses, run bulk verification jobs and check your credit balance through your EzVerify account.
What is EzVerify MCP Server?
EzVerify MCP Server is a Model Context Protocol (MCP) server that connects Claude and other MCP clients to the EzVerify email verification API. It lets the assistant verify email addresses, submit bulk verification jobs and read your account information on your behalf, from a plain-language conversation.
It calls the EzVerify REST API with your API key, so it needs an EzVerify account on the Starter or Business plan.
Related MCP server: unpublished
Setup
Requires a Starter or Business plan and Node.js 18+. Generate an API key on the API Usage page of your EzVerify dashboard (Dashboard → API Usage). It is shown once, so store it safely; regenerate it if you lose it.
Claude Desktop
Add to claude_desktop_config.json:
Windows:
%APPDATA%\Claude\claude_desktop_config.jsonmacOS:
~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"ezverify": {
"command": "npx",
"args": ["-y", "ezverify-mcp"],
"env": {
"EZVERIFY_API_KEY": "YOUR_EZVERIFY_API_KEY"
}
}
}
}Restart Claude Desktop after saving.
Claude Code
Add a .mcp.json file at your project root:
{
"mcpServers": {
"ezverify": {
"command": "npx",
"args": ["-y", "ezverify-mcp"],
"env": {
"EZVERIFY_API_KEY": "YOUR_EZVERIFY_API_KEY"
}
}
}
}Your key is in that file, so do not commit it to source control.
Other MCP clients
Any client that can start a stdio MCP server works the same way: run npx -y ezverify-mcp with the EZVERIFY_API_KEY environment variable set.
How to Use
Once configured, ask your assistant to verify emails in plain English. For example:
"Verify this email address for me"
"Check which of these 20 emails are valid"
"How many credits do I have left?"
Key Features
Verify a single email address and get a full result including status, deliverability score and detailed flags
Submit bulk email lists for async verification and poll for results when complete
Results include disposable-domain, role-account and typo-suggestion flags
Check your credit usage and remaining balance without logging into the dashboard
Retrieve your current plan and account information on demand
Your API key stays in your local configuration and is sent only to
ezverify.app; the server does not store or log it
Available Tools
Tool | Description | Credits |
| Verify a single email: status, score, flags | Uses credits |
| Submit an async bulk verification job (up to 1,000 emails per request) | Uses credits |
| Poll bulk job progress and results | Free |
| Request statistics over the last N days (single verifications; credits spent by bulk jobs are not included) | Free |
| Plan, credits used this month, credits remaining, monthly limit | Free |
The three read-only tools are marked readOnlyHint in the tool metadata. verify_email and verify_emails_bulk are not, because they spend credits, so clients that ask for confirmation before non-read-only tools will ask before running them.
Limits
verify_emailis limited to 100 calls per hour per account (the API answers429 rate_limit_exceeded). The other tools are not limited per hour.A bulk job takes up to 1,000 emails per request. Duplicates within one request are verified and billed once.
A bulk
webhook_urlmust be a publichttp(s)address. It gets one POST when the job completes, with counts only (campaign_id, which equals therequest_id, and the valid/invalid/risky/unknown totals), not per-address results: fetch those withget_bulk_job_status. It is attempted once and not retried.An account that is restricted (for example after repeated declined payments) gets
402 account_restrictedon the two verification tools; the read-only tools still work.
Use Cases
Ask Claude to clean an email list before a campaign launch and return only the valid addresses
Verify a prospect's email address mid-conversation while researching leads
Check whether a submitted email is real before triggering an onboarding workflow
Ask Claude how many credits you have left before running a large verification job
Bulk verify emails pasted directly into the chat and get a formatted summary of results
Example Prompts
"Verify john@example.com — is it safe to send to?"
"Bulk verify these 20 emails and return only the valid ones."
"How many credits have I used this month?"
"What plan am I on and how many credits are left this month?"
HTTP mode (self-hosting)
By default the server talks to the client over stdio. To run it as a small HTTP service instead, set PORT:
PORT=3100 npx -y ezverify-mcpIt listens on
127.0.0.1unless you setHOST. Put a TLS reverse proxy in front of it if you expose it beyond your machine.MCP endpoint:
POST /mcp(Streamable HTTP, stateless: every request gets its own server instance, there are no sessions).GETandDELETEanswer405.Each caller sends its own EzVerify API key in an
X-Api-Keyheader. The service has no key of its own and never falls back to one from its environment, soEZVERIFY_API_KEYis not used in this mode. A call without the header gets amissing_api_keytool error.Requests that carry an
Originheader (browsers) are refused with403, and a request body over 1 MB with413. Clients that can only authenticate with OAuth are not supported.GET /healthreturns{"status":"ok",...}for monitoring.
FAQ
Do I need to install anything?
Node.js 18 or newer. The server runs through npx, which downloads and starts it on demand, so there is no separate install step.
Where do I get my API key? Log in to your EzVerify dashboard at ezverify.app, open API Usage (ezverify.app/Dashboard/ApiUsage) and generate a key there. It is shown once, so copy it and store it safely; if you lose it, regenerate it on the same page. API keys only work on the Starter and Business plans.
Does this use my EzVerify credits?
Yes, verify_email and verify_emails_bulk do. They use the same credits as a direct API call, at your plan's rates. valid, invalid and risky results use a credit; unknown results are free. Checking the same address in a separate call is charged again.
Is my API key safe? The server reads your API key from your local configuration and sends it only to the EzVerify API. It does not store or log it. Treat the key like a password, and regenerate it on the API Usage page if it leaks.
Can I use this with Claude Code?
Yes. Add a .mcp.json file to your project root with the configuration above.
What happens if I use more than my monthly credits?
Nothing stops. Credits are counted per calendar month (UTC) and reset on the 1st; unused credits do not roll over. Usage beyond your plan's monthly credits is billed as overage at your plan's per-credit rate (Starter $0.004, Business $0.002); you are charged after the month ends, never up front. Check your balance any time with get_account_info.
Requirements
Node.js 18+
An EzVerify account on the Starter or Business plan (the API and this MCP server are not available on the Free plan)
License
Available Tools
5 toolsget_account_infoGet account and credit balanceARead-only
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.
Inputs: no named parameters.
get_bulk_job_statusCheck a bulk verification jobARead-only
Check the status of a bulk verification job. Returns progress, counts, and full results when completed. Free: does not use credits.
Inputs: request_id (required).
get_usage_statsGet request statisticsARead-only
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.
Inputs: days.
verify_emailVerify an email addressA
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.
Inputs: email (required).
verify_emails_bulkVerify a list of email addresses (bulk job)A
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.
Inputs: emails (required), webhook_url.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
Unofficial Emailable MCP — wraps the Emailable email verification API (emailable.com)
Unofficial MillionVerifier MCP — wraps the MillionVerifier single-verify API (millionverifier.com)
Verify emails and domains for routing, disposable providers, role accounts, and SMTP risk.
Unofficial BounceBan MCP — wraps the BounceBan email-verification API (bounceban.com)
Related MCP Servers
- AlicenseAqualityDmaintenanceEnables real-time email verification via MCP tools, checking syntax, MX, disposable domains, and optional SMTP probe to determine deliverability with a VALID/RISKY/INVALID verdict.23 npmMIT
- MIT
- FlicenseAqualityBmaintenanceEnables email address verification through a single MCP tool, returning whether an address is valid, invalid, or risky.1-
- AlicenseAqualityCmaintenanceEnables MCP clients such as Claude Code or Claude Desktop to verify whether email addresses are deliverable, returning status, sub-status, reason, confidence, and metadata.111 npmISC