Vexa
Meeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.
Description from the maker (original English)
Pay-per-call MCP server. $0.03 USDC sends one transactional SMS to a US phone number via x402.
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.
BUYER_PRIVATE_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": {
"x402-sms": {
"command": "npx",
"args": [
"-y",
"x402-sms-mcp"
],
"env": {
"BUYER_PRIVATE_KEY": "your-value"
}
}
}
}Run this in your terminal
claude mcp add x402-sms --env BUYER_PRIVATE_KEY=your-value -- npx -y x402-sms-mcpFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"x402-sms": {
"command": "npx",
"args": [
"-y",
"x402-sms-mcp"
],
"env": {
"BUYER_PRIVATE_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": {
"x402-sms": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"x402-sms-mcp"
],
"env": {
"BUYER_PRIVATE_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 9, 2026
The registry name was verified with the GitHub account UltraStarz, which owns the repo
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 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: BUYER_PRIVATE_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 (0.1.0) reached the registry 6 months 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.
A paid MCP server that lets AI agents send SMS messages to US phone numbers.
Each send_sms tool call:
Reply STOP to opt out if the body doesn't include opt-out languageNo API keys. No Twilio account. The agent pays the toll, the message goes out.
Status (2026-05-22): Public beta on Base Sepolia (testnet). The seller's toll-free number is undergoing Twilio TFV approval (submitted 2026-05-14, still in queue). During this window
/sendcalls short-circuit to a503 delivery_pending_tfv_approvalresponse before the buyer wallet signs anything, so no USDC is moved. The day Twilio approves the number, delivery flips on; pricing flips to Base mainnet shortly after.
Add this to your MCP config (~/Library/Application Support/Claude/claude_desktop_config.json on macOS):
{
"mcpServers": { "x402-sms": { "command": "npx", "args": ["-y", "x402-sms-mcp"], "env": { "BUYER_PRIVATE_KEY": "0xYOUR_PRIVATE_KEY" } } } }
Restart your MCP client. A send_sms tool will appear.
A wallet on Base Sepolia (testnet) funded with:
Generate a throwaway key:
node -e "const {generatePrivateKey,privateKeyToAccount}=require('viem/accounts');const k=generatePrivateKey();console.log('PRIVATE_KEY=',k);console.log('ADDRESS=',privateKeyToAccount(k).address)"
Use the printed address to claim from faucets, then put the printed key into your MCP config.
In Claude Desktop, ask:
Text my cell at +15551234567 when this long-running task finishes. The recipient (me) consents to receive this message.
Claude will call send_sms with opt_in_attestation: true. You'll get back a Twilio SID + the on-chain settlement hash. The transfer is visible at https://sepolia.basescan.org.
This MCP wraps a regulated SMS gateway. The operator (you) is responsible for ensuring every recipient has consented to receive messages before invoking send_sms. The opt_in_attestation: true argument is your legal attestation under TCPA and CTIA short-code/long-code rules.
Do NOT use this MCP to:
+1 E.164)The seller-side automatically:
Reply STOP to opt out to every messageIf you have any doubt about consent, do not call this tool.
| Env var | Required | Default |
|---|---|---|
BUYER_PRIVATE_KEY | yes | — |
SMS_URL | no | https://x402-sms-server-production.up.railway.app/send |
To point the MCP server at your own seller deployment, override SMS_URL.
The MCP surfaces three distinct error shapes so the model can explain what happened to the user and decide whether to retry.
| Cause | What you'll see in chat | Was payment taken? |
|---|---|---|
Seller's toll-free number still in TFV review (HTTP 503) | "SMS not sent — service is in pre-launch wait" + the seller's submitted date and retry guidance | no |
Buyer wallet exceeded per-minute/hour/day rate limit (HTTP 429) | "SMS not sent — this buyer wallet hit the per-X rate limit" + retry_after_seconds | no |
Twilio-side rejection (e.g. invalid number 21211, opted-out 21610) | Friendly hint mapped from the Twilio error code + the full response body | yes (the send tried) |
For the full mapping of Twilio error codes the MCP recognizes, see TWILIO_HINTS in src/index.ts.
Claude Desktop ──tool call──> MCP server (this package, on your machine)
│ │ x402 payment (USDC, Base Sepolia) │ + to/message/opt_in_attestation ▼ Public seller (Hono + Twilio on Railway) │ │ Twilio dispatch ▼ SMS lands on recipient's phone │ │ Twilio SID + status ▼ MCP server ──tool result──> Claude Desktop
The MCP server doesn't talk to Twilio directly. It signs an x402 payment with the buyer's wallet, sends the payment + message details to the seller endpoint, and the seller's toll-free number dispatches the SMS. Your private key never leaves your machine. The seller never sees it.
MIT