Vexa
Meeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.
Description from the maker (original English)
Email verification for AI agents — verify, clean & validate emails; self-onboard + crypto pay
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.
AuthorizationValues 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 …”.
This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.
Run this in your terminal
claude mcp add --transport http verifly https://verifly.email/mcp --header 'Authorization: your-value'Fill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"verifly": {
"url": "https://verifly.email/mcp",
"headers": {
"Authorization": "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": {
"verifly": {
"type": "http",
"url": "https://verifly.email/mcp",
"headers": {
"Authorization": "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 address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.
Your choice stays on this device in a cookie; no account needed.
Authorization secret required HTTP headerThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
We have not read this server’s tool list yet; we check endpoints in rotation.
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 against the domain verifly.email (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Not checked yet; we check endpoints in rotation
Not checked yet; we check endpoints in rotation
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 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: Authorization
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed –, and the latest version (1.0.0) reached the registry 4 months 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:↓ 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.
Agent-native email verification over the Model Context Protocol. This server gives any MCP client — Cline, Claude Desktop, Claude Code, Cursor, Windsurf — a clean set of tools to verify email addresses, clean lists, run async bulk jobs, and manage a Verifly account, all without writing a single raw HTTP call.
It is built for autonomous workflows: an agent can self-register for an API key, verify a lead before sending, deduplicate and scrub an import list, kick off a bulk job and poll it to completion, and check its own credits and usage — end to end.
15 tools cover the full Verifly workflow:
| Tool | What it does |
|---|---|
verify_email | Verify a single address in real time (verdict, reason, flags, send/reject recommendation, credits) |
verify_batch | Verify a list synchronously (per-address verdicts; best for up to a few hundred) |
clean_email_list | Dedupe + drop invalid syntax, disposable, and role addresses from a list |
extract_emails | Pull every email address out of free-form text (notes, signatures, pasted docs) |
check_domain_health | MX / SPF / DMARC records + an overall health score for a domain |
get_credits | Remaining verification credits + recent usage (free, no credits) |
submit_bulk | Submit an async bulk verification job for large lists (returns a job_id; optional webhook_url) |
get_job_status | Status + progress of a bulk job |
get_job_results | Per-address results of a completed bulk job |
list_jobs | List the account's bulk jobs (filter by status, paginate) |
get_usage | Detailed usage statistics for a period (day / week / month) |
get_account | Account profile: email, company, credits, plan, key count (free) |
get_packages | List the credit packages available to purchase |
buy_credits | Start a credit-package purchase and return a checkout link |
register_account | Self-onboard a brand-new account; returns an api_key shown once |
Get an API key from https://verifly.email (or have an agent self-register with register_account). The server reads the key from the VERIFLY_API_KEY environment variable. Every Verifly request is authenticated with Authorization: Bearer .
The hosted HTTP transport also accepts a per-request Authorization: Bearer header (which overrides the env var), so each caller can supply their own key.
npx -y verifly-mcp-server
or install it globally:
npm install -g verifly-mcp-server
verifly-mcp-server
Add this to your MCP client config (Cline: cline_mcp_settings.json; Claude Desktop: claude_desktop_config.json):
{
"mcpServers": { "verifly": { "command": "npx", "args": ["-y", "verifly-mcp-server"], "env": { "VERIFLY_API_KEY": "vf_your_api_key" } } } }
That's the whole setup — no build step, no clone. See llms-install.md for an agent-followable install guide.
If you'd rather not run anything locally, Verifly hosts the same server as a remote Streamable-HTTP endpoint:
https://verifly.email/mcp
Point any Streamable-HTTP-capable MCP client at that URL and pass your key as an Authorization: Bearer header. Example raw call:
curl -s -X POST https://verifly.email/mcp \
-H "Content-Type: application/json" \ -H "Accept: application/json, text/event-stream" \ -H "Authorization: Bearer vf_your_api_key" \ -d '{"jsonrpc":"2.0","id":1,"method":"tools/call", "params":{"name":"verify_email","arguments":{"email":"lead@example.com"}}}'
PORT=8787 VERIFLY_API_KEY=vf_your_api_key node src/http.js
| Var | Default | Purpose |
|---|---|---|
PORT | 8787 | Listen port |
HOST | 0.0.0.0 | Bind address |
MCP_PATH | /mcp | Path the MCP endpoint is served on |
VERIFLY_API_KEY | — | Fallback key when a request sends no Authorization header |
VERIFLY_BASE_URL | https://verifly.email | API base override |
POST {MCP_PATH} (stateless Streamable HTTP).GET /healthz → {"ok":true}.VERIFLY_API_KEY=vf_your_api_key npm run test:e2e
Drives the stdio server through the MCP protocol and performs a real verify_email + get_credits call against the live API.
MIT