Vexa
Meeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.
Description from the maker (original English)
Verify email lists on your own ZeroBounce, NeverBounce, MillionVerifier, BounceBan, or Reoon key.
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.
APIFY_TOKEN, EMAIL_VERIFIER_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": {
"email-verifier": {
"command": "npx",
"args": [
"-y",
"@mambalabsdev/mcp-email-verifier"
],
"env": {
"APIFY_TOKEN": "your-value",
"EMAIL_VERIFIER_API_KEY": "your-value"
}
}
}
}Run this in your terminal
claude mcp add email-verifier --env APIFY_TOKEN=your-value --env EMAIL_VERIFIER_API_KEY=your-value -- npx -y @mambalabsdev/mcp-email-verifierFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"email-verifier": {
"command": "npx",
"args": [
"-y",
"@mambalabsdev/mcp-email-verifier"
],
"env": {
"APIFY_TOKEN": "your-value",
"EMAIL_VERIFIER_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": {
"email-verifier": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@mambalabsdev/mcp-email-verifier"
],
"env": {
"APIFY_TOKEN": "your-value",
"EMAIL_VERIFIER_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 8, 2026
The publisher (mambabuilt.com) is not the repo owner (mambalabsdev); someone else may have listed it
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 0 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: APIFY_TOKEN, EMAIL_VERIFIER_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.1) reached the registry 3 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.
An MCP server for the Mamba Labs Email List Verifier, Bring Your Own Key actor on Apify. Give it a list of email addresses and it checks each one with the verification service you already pay for: ZeroBounce, NeverBounce, MillionVerifier, BounceBan, or Reoon Email Verifier. You supply the service key.
verdict (valid, invalid, catch_all, risky, or unknown), the service's own provider_status and provider_sub_status, is_role, is_free_email, is_disposable, and did_you_mean for a spelling fix.Bad input returns one free row whose error_reason starts with input_invalid:. With no key set, the tool refuses before any run starts, so nothing is charged.
All of the work runs on Apify. This package is a thin client that starts the actor run, waits for it, and hands back the dataset rows.
You need Node.js 18 or newer, an Apify account with an API token, and an API key for one of the five services.
Add this to your Claude Desktop config (claude_desktop_config.json), Cursor, or any MCP client:
{
"mcpServers": { "mamba-email-verifier": { "command": "npx", "args": [ "-y", "@mambalabsdev/mcp-email-verifier" ], "env": { "APIFY_TOKEN": "your-apify-token", "EMAIL_VERIFIER_API_KEY": "your-verification-service-key" } } } }
Restart the client. The verify_emails tool appears.
APIFY_TOKEN. The server lists its tool without a token; a call needs one.EMAIL_VERIFIER_API_KEY.verify_emails. One tool. Example arguments:
{
"emails": [ "jane@example.com", "sales@example.org" ], "provider": "neverbounce" }
Every buyer facing input of the actor except api_key, which comes from EMAIL_VERIFIER_API_KEY in the server environment so it never passes through the conversation. Omitted inputs take the actor's own defaults. Numbers are sent as strings.
| Input | Type | Description |
|---|---|---|
emails | array | Required. The addresses to verify, 1 to 5,000 per run |
email | string | One more address, added to emails |
provider | string | zerobounce (default), neverbounce, millionverifier, bounceban, or reoon. The service your key belongs to |
concurrency | string | Addresses checked at the same time, 1 to 20. Default 5 |
max_charge_usd | string | Optional. The run stops before an actor charge that would pass this amount |
Two separate bills. Your verification service bills each check to your account there, at your plan's price. The actor charges per event on Apify, billed to your Apify account. Prices in USD.
| Event | Free plan | Bronze | Silver | Gold |
|---|---|---|---|---|
email-verified, one address your service answered valid, invalid, catch all, or risky | $0.0016 | $0.00152 | $0.00144 | $0.00136 |
apify-actor-start, per run start | $0.0006 | $0.0006 | $0.0006 | $0.0006 |
Unknown answers, error rows, addresses with broken syntax, repeats in the same run, and refused input are free. Mamba Labs pays the Apify platform costs of the run.
The key is read from this server's environment and passed in the run input as a secret field. The actor sends it only to the service you chose and never logs, stores, or returns it. Apify blocks the outbound mail port, so every mailbox check runs at your service.
apify.com/mambalabs/email-verifier
MIT. See LICENSE.