Vexa
Meeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.
Description from the maker (original English)
Give an AI agent a throwaway email and phone number to test signup/verification flows end to end.
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://api.flo-voice1.com/mcpRun this in your terminal
claude mcp add --transport http agent-identity https://api.flo-voice1.com/mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"agent-identity": {
"url": "https://api.flo-voice1.com/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": {
"agent-identity": {
"type": "http",
"url": "https://api.flo-voice1.com/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://api.flo-voice1.com/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 9, 2026
The publisher (flo-voice1.com) is not the repo owner (flovoice53-tech); someone else may have listed it
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Responded in 95 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 2 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.
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 (0.1.6) 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:↓ 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.
MCP server that gives an AI agent a throwaway test identity — a real disposable email address and a real UK phone number — so it can sign up for something it's testing and read back the verification email/SMS itself, without a human in the loop.
Bundles two existing services:
create_test_email no longer needs any receivemail.dev credential — mailbox creation is public/self-serve (rate-limited: 20/min per IP, 5,000/day total). The only credential needed is your own SMS_FLORIN_API_KEY, for the phone-number tools.
{
"mcpServers": { "agent-identity": { "command": "npx", "args": ["-y", "agent-identity-mcp"], "env": { "SMS_FLORIN_API_KEY": "your_key_here" } } } }
| Tool | Description |
|---|---|
create_test_email | Get a fresh disposable email address, valid up to 60 minutes. |
get_test_email_messages | Read what's arrived on an address created above. |
list_services | List services a phone number can be rented for. |
rent_test_phone_number | Rent a real UK number for a service. Costs balance. |
wait_for_test_sms | Block until the SMS/OTP code arrives. |
list_esim_plans | List travel eSIM data plans (data only, no SMS). |
get_esim_checkout_link | Get a Stripe checkout link for an eSIM plan, for the user to pay. |
get_usage_stats | See how many times each tool was called — today, last 7 and last 30 days. On the hosted server it's per API key and survives restarts; locally it counts since the MCP client started the server. Failed calls aren't counted. |
Building or testing an AI shopping agent (ACP/agentic commerce)? acp-sandbox is a hosted mock merchant your agent can complete a full test checkout against — no real store, no real money. Combined with this package, an agent gets a disposable email/phone for the buyer identity *and* a merchant to actually check out with, entirely test-side.
Ship your own signup/verification flow? otp-watch uses the same underlying real phone numbers and disposable mailboxes to answer a different question: is your OTP/verification SMS or email actually arriving, and how fast? Point your own cron/CI at it to catch a broken delivery pipeline before your users do.
MIT