Vexa
Meeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.
Description from the maker (original English)
Find and verify B2B work emails, single or bulk. OAuth sign-in or API key; pay per verified email.
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 findleademails https://www.findleademails.com/api/mcp --header 'Authorization: Bearer {api_key}'Fill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"findleademails": {
"url": "https://www.findleademails.com/api/mcp",
"headers": {
"Authorization": "Bearer {api_key}"
}
}
}
}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": {
"findleademails": {
"type": "http",
"url": "https://www.findleademails.com/api/mcp",
"headers": {
"Authorization": "Bearer {api_key}"
}
}
}
}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 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 7, 2026
The registry name was verified against the domain findleademails.com (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.1.0) reached the registry 18 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.
Find and verify B2B work emails from your AI assistant: single lookups or bulk lists, with deliverability checks.
This repository holds setup docs and config for the hosted FindLeadEmails MCP server. There is no code to install: the server is remote.
https://www.findleademails.com/api/mcp (Streamable HTTP)Authorization: Bearer YOUR_API_KEY. Listing tools (initialize, tools/list) needs neither.Use the www host. https://findleademails.com redirects, and some clients drop the Authorization header when following that redirect.
Both buttons add the server URL only. Approve the OAuth sign-in in your browser the first time a tool runs.
| Tool | What it does | Credits |
|---|---|---|
find_email | Find and verify one person's work email from first_name, last_name, company_domain (or a LinkedIn company page URL). | 1 only when the mailbox is verified |
verify_email | Check one email you already have. | 1 only when confirmed valid |
find_emails_bulk | Find and verify a batch in one synchronous call (capped; returns batch_too_large above the cap). | 1 per verified result |
create_job | Queue a large list for background processing; returns a job id. | Reserves 1 per row, refunds unused |
get_job_status | Progress and per-outcome counters for a job. | Free |
get_job_results | A page of per-row results (page with cursor until next_cursor is null). Works while running. | Free |
Pricing: misses, catch-alls, predicted results and repeat lookups are free; you pay only for verified emails. Credits never expire. See https://www.findleademails.com/docs/mcp?utm_source=github#credits.
The server supports OAuth 2.1 with PKCE (S256), Client ID Metadata Documents, and Dynamic Client Registration. In a client that supports OAuth, add the URL with no Authorization header and approve access in your browser. No API key needed.
https://www.findleademails.com/api/mcp, choose "Sign in when needed", and keep "Use Claude's published identity". claude mcp add --transport http findleademails https://www.findleademails.com/api/mcp
Then run /mcp in Claude Code, select findleademails, and choose Authenticate.
headers (or use the install buttons above). The client opens the sign-in page when needed./mcp auth findleademails.Prefer an API key? Use the snippets below.
Replace YOUR_API_KEY with your key in every snippet.
For OAuth, use the Add to Cursor button above. For an API key, add this by hand to .cursor/mcp.json (project) or ~/.cursor/mcp.json (global). The same file is in this repo as .mcp.json.
{
"mcpServers": { "findleademails": { "url": "https://www.findleademails.com/api/mcp", "headers": { "Authorization": "Bearer YOUR_API_KEY" } } } }
To keep the key out of the file, use "Bearer ${env:FINDLEADEMAILS_API_KEY}".
claude mcp add --transport http findleademails https://www.findleademails.com/api/mcp --header "Authorization: Bearer YOUR_API_KEY"
Claude Desktop needs the mcp-remote bridge (Node.js 18+). In claude_desktop_config.json:
{
"mcpServers": { "findleademails": { "command": "npx", "args": ["-y", "mcp-remote", "https://www.findleademails.com/api/mcp", "--header", "Authorization:${AUTH_HEADER}"], "env": { "AUTH_HEADER": "Bearer YOUR_API_KEY" } } } }
.vscode/mcp.json. VS Code prompts for the key and stores it securely:
{
"inputs": [ { "type": "promptString", "id": "findleademails-api-key", "description": "Paste your FindLeadEmails API key.", "password": true } ], "servers": { "findleademails": { "type": "http", "url": "https://www.findleademails.com/api/mcp", "headers": { "Authorization": "Bearer ${input:findleademails-api-key}" } } } }
mcp_config.json (open it from the Cascade panel's actions menu; on macOS/Linux ~/.config/devin/mcp_config.json, on Windows %APPDATA%\devin\mcp_config.json):
{
"mcpServers": { "findleademails": { "serverUrl": "https://www.findleademails.com/api/mcp", "headers": { "Authorization": "Bearer YOUR_API_KEY" } } } }
Ask Cline to install this server from this repo (it follows llms-install.md), or add to cline_mcp_settings.json:
{
"mcpServers": { "findleademails": { "type": "streamableHttp", "url": "https://www.findleademails.com/api/mcp", "headers": { "Authorization": "Bearer YOUR_API_KEY" } } } }
gemini extensions install https://github.com/findleademails/findleademails-mcp
The CLI asks for your API key during install and stores it in the system keychain. Change it later with gemini extensions config findleademails.
Pro, Max or Enterprise: Connectors → add a custom remote connector and choose the authentication option your plan offers. With an API key:
URL: https://www.findleademails.com/api/mcp
Header: Authorization: Bearer YOUR_API_KEY
On grok.com: Connectors → New Connector → Custom, enter the server URL, and paste the API key when asked for authentication. Business and Enterprise workspaces need an admin to provision custom connectors first.
Grok CLI:
grok mcp add --transport http findleademails https://www.findleademails.com/api/mcp --header "Authorization: Bearer YOUR_API_KEY"
xAI API (the key goes in authorization without the word Bearer):
{
"type": "mcp", "server_url": "https://www.findleademails.com/api/mcp", "server_label": "findleademails", "authorization": "YOUR_API_KEY" }
A client that supports OAuth only needs the URL. Any client that takes a remote URL plus headers: use the Cursor JSON above, adjusted to that client's key names.
curl https://www.findleademails.com/api/mcp \
-H "Content-Type: application/json" \ -H "Accept: application/json, text/event-stream" \ -d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'
A tool call without a key or OAuth token returns HTTP 401 invalid_token (with a WWW-Authenticate header pointing OAuth clients to sign-in) and nothing is charged. A POST without Accept: application/json, text/event-stream returns 406.
MIT. See LICENSE.
— The FindLeadEmails team