Vexa
Meeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.
Description from the maker (original English)
Verify email addresses with EzVerify. Needs an EzVerify Starter or Business plan.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
EZVERIFY_API_KEYValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"ezverify": {
"command": "npx",
"args": [
"-y",
"ezverify-mcp"
],
"env": {
"EZVERIFY_API_KEY": "your-value"
}
}
}
}Run this in your terminal
claude mcp add ezverify --env EZVERIFY_API_KEY=your-value -- npx -y ezverify-mcpFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"ezverify": {
"command": "npx",
"args": [
"-y",
"ezverify-mcp"
],
"env": {
"EZVERIFY_API_KEY": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"ezverify": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"ezverify-mcp"
],
"env": {
"EZVERIFY_API_KEY": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 9, 2026
The registry name was verified with the GitHub account jefferyleo, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: EZVERIFY_API_KEY
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (1.0.10) reached the registry 2 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Vexa, emailmd, MCP WhatsApp Cloud
Servers in the same category from other makers, sorted by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Meeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.
Render markdown into email-safe HTML, lint drafts for deliverability problems, and preview emails.
MCP server for WhatsApp Cloud API (Meta) — messages, media, and templates via Graph API
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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.
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.
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.
Add to claude_desktop_config.json:
%APPDATA%\Claude\claude_desktop_config.json~/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.
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.
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.
Once configured, ask your assistant to verify emails in plain English. For example:
ezverify.app; the server does not store or log it| Tool | Description | Credits |
|---|---|---|
verify_email | Verify a single email: status, score, flags | Uses credits |
verify_emails_bulk | Submit an async bulk verification job (up to 1,000 emails per request) | Uses credits |
get_bulk_job_status | Poll bulk job progress and results | Free |
get_usage_stats | Request statistics over the last N days (single verifications; credits spent by bulk jobs are not included) | Free |
get_account_info | 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.
verify_email is limited to 100 calls per hour per account (the API answers 429 rate_limit_exceeded). The other tools are not limited per hour.webhook_url must be a public http(s) address. It gets one POST when the job completes, with counts only (campaign_id, which equals the request_id, and the valid/invalid/risky/unknown totals), not per-address results: fetch those with get_bulk_job_status. It is attempted once and not retried.402 account_restricted on the two verification tools; the read-only tools still work.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-mcp
127.0.0.1 unless you set HOST. Put a TLS reverse proxy in front of it if you expose it beyond your machine.POST /mcp (Streamable HTTP, stateless: every request gets its own server instance, there are no sessions). GET and DELETE answer 405.X-Api-Key header. The service has no key of its own and never falls back to one from its environment, so EZVERIFY_API_KEY is not used in this mode. A call without the header gets a missing_api_key tool error.Origin header (browsers) are refused with 403, and a request body over 1 MB with 413. Clients that can only authenticate with OAuth are not supported.GET /health returns {"status":"ok",...} for monitoring.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.
MIT