Pay-per-call MCP server. $0.03 USDC sends one transactional SMS to a US phone number via x402.
MCPpedia last refreshed this data
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"x402-sms": {
"env": {
"BUYER_PRIVATE_KEY": "0xYOUR_PRIVATE_KEY"
},
"args": [
"-y",
"x402-sms-mcp"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
A paid MCP server that lets AI agents send SMS messages to US phone numbers.
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in finance
Let AI agents create, discover, and track tokens across chains via Printr.
Real-time financial market data: stocks, forex, crypto, commodities, and economic indicators
Swiss accounting integration for Bexio. 310 tools for invoices, contacts, projects.
Brazilian public procurement (PNCP) and Federal Revenue CNPJ data — 16 tools, 4 prompts.
MCP Security Weekly
Get CVE alerts and security updates for io.github.UltraStarz/x402-sms and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
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? | | ----------------------------------------------------