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: check addresses and lists, priced before credits are spent.
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 listcheckup https://listcheckup.com/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": {
"listcheckup": {
"url": "https://listcheckup.com/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": {
"listcheckup": {
"type": "http",
"url": "https://listcheckup.com/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 6, 2026
The registry name was verified against the domain listcheckup.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.0.0) reached the registry 10 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.
Email verification for AI assistants. Connect Claude, Cursor or any MCP client to ListCheckup and let it check a single address or a whole list, showing you the price before anything is spent.
https://listcheckup.com/mcp (remote, Streamable HTTP)Authorization: Bearer lck_live_... (create a key in your ListCheckup dashboard)| Tool | What it does | Cost |
|---|---|---|
check_email | Verify one address: valid, invalid, risky, catch-all or unknown, with the reason and a confidence score | 1 credit (free if catch-all or unknown) |
get_balance | Credits left on the account | Free |
create_list | Submit a list and get its price | Free |
start_list | Start checking a list you've priced | Spends credits |
get_list | Status and progress of a list | Free |
get_list_summary | Counts by status once a list is finished | Free |
Pricing and starting are separate tools on purpose: an assistant has to show you what a list will cost before anything is spent, and you can say no. No tool takes an account as an argument; the key in the header decides whose credits are used.
Claude Code
claude mcp add --transport http listcheckup https://listcheckup.com/mcp \
--header "Authorization: Bearer lck_live_..."
Claude Desktop, Cursor and most other clients
{
"mcpServers": { "listcheckup": { "url": "https://listcheckup.com/mcp", "headers": { "Authorization": "Bearer lck_live_..." } } } }
Check it works
curl -X POST "https://listcheckup.com/mcp" \
-H "Authorization: Bearer lck_live_..." \ -H "Content-Type: application/json" \ -H "Accept: application/json, text/event-stream" \ -d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'
Six tools listed means you're connected.
Anything holding it can spend your credits. Keep config files with the key out of shared repositories, give each machine its own key, and revoke a key in the dashboard if it leaks. Revoking takes effect immediately.
ListCheckup checks addresses you already hold. Purchased, rented or scraped lists aren't allowed under the acceptable use policy.