Vexa
Meeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.
Description from the maker (original English)
Real-time email verification and deliverability diagnostics (MX, SPF, DKIM, DMARC).
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.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
https://mcp.verifyany.email/mcpOpen Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"verifyanyemail": {
"command": "npx",
"args": [
"-y",
"verifyanyemail-mcp"
]
}
}
}Run this in your terminal
claude mcp add --transport http verifyanyemail https://mcp.verifyany.email/mcpclaude mcp add verifyanyemail -- npx -y verifyanyemail-mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"verifyanyemail": {
"url": "https://mcp.verifyany.email/mcp"
}
}
}Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"verifyanyemail": {
"command": "npx",
"args": [
"-y",
"verifyanyemail-mcp"
]
}
}
}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": {
"verifyanyemail": {
"type": "http",
"url": "https://mcp.verifyany.email/mcp"
}
}
}Paste into .vscode/mcp.json in your project
{
"servers": {
"verifyanyemail": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"verifyanyemail-mcp"
]
}
}
}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.
ChatGPT connects only to servers on the internet:
https://mcp.verifyany.email/mcpMenu names can differ slightly by plan and over time.
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.
The server asks you to sign in before it lists its tools.
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 7, 2026
The registry name was verified with the GitHub account verifyanyemail, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Responded in 121 ms (HTTP 401)
Declares OAuth sign-in, so your AI app can take you to log in
Not checked yet; we read the tool list when we check the endpoint
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 3 of 3 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.
The registry does not list a required key, though some servers ask you to sign in on first use.
Either way works: install it on your computer or connect to the cloud version.
The GitHub repo last changed –, and the latest version (1.2.3) reached the registry 7 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Vexa, emailmd, MCP WhatsApp Cloud
Servers in the same category from other makers, sorted by stars.
Reading a card:★ 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.
Official Model Context Protocol server for VerifyAnyEmail — give any AI agent real-time email verification and deliverability diagnostics.
Works with Claude Desktop, Claude Code, Cursor, Windsurf, ChatGPT (MCP connectors), and any other MCP client.
| Tool | Description | Credits |
|---|---|---|
verify_email | Verify one address — verdict (deliverable/undeliverable/risky/unknown), 0–100 score, safeToSend, and signals (catch-all, disposable, role-based, typo). | 1 per call |
verify_batch | Submit many addresses for async bulk verification; returns a batchId. | 1 per address |
get_batch_status | Poll a batch's progress and per-status counts. | free |
get_batch_results | Fetch a paginated page of batch results. | free |
check_mx | Domain MX records / can it receive mail. | free |
check_spf | SPF record + misconfiguration flags. | free |
check_dmarc | DMARC policy and alignment. | free |
check_dkim | DKIM record for a selector. | free |
check_domain_health | Combined MX/SPF/DKIM/DMARC health grade with findings. | free |
The diagnostics are free (no verification credits). Verification spends credits — except test addresses at test.verifyany.email (deliverable@, undeliverable@, risky@, unknown@), which return canned results and cost 0 credits, perfect for trying it out.
You need a VerifyAnyEmail API key (vae_…) — create one in the dashboard → API Keys.
The server is distributed on npm and runs with npx (no install needed).
Edit claude_desktop_config.json (Settings → Developer → Edit Config):
{
"mcpServers": { "verifyanyemail": { "command": "npx", "args": ["-y", "verifyanyemail-mcp"], "env": { "VERIFYANYEMAIL_API_KEY": "vae_your_key_here" } } } }
Restart Claude Desktop. You'll see the VerifyAnyEmail tools available.
claude mcp add verifyanyemail -e VERIFYANYEMAIL_API_KEY=vae_your_key_here -- npx -y verifyanyemail-mcp
Add to ~/.cursor/mcp.json (or a project .cursor/mcp.json):
{
"mcpServers": { "verifyanyemail": { "command": "npx", "args": ["-y", "verifyanyemail-mcp"], "env": { "VERIFYANYEMAIL_API_KEY": "vae_your_key_here" } } } }
Run the binary over stdio with the API key in the environment:
VERIFYANYEMAIL_API_KEY=vae_your_key_here npx -y verifyanyemail-mcp
| Env var | Required | Default | Purpose |
|---|---|---|---|
VERIFYANYEMAIL_API_KEY | ✅ | — | Your vae_… API key. |
VERIFYANYEMAIL_BASE_URL | — | https://api.verifyany.email | Override the API base URL. |
VERIFYANYEMAIL_TIMEOUT_MS | — | 30000 | Per-request timeout in milliseconds. |
jane.doe@acme.com a real, safe-to-send address?"verify_batch)example.com."example.com have a valid SPF and DMARC setup?"MIT © VerifyAnyEmail