Server data from the Official MCP Registry
Pay-per-call MCP server. $0.03 USDC sends one transactional SMS to a US phone number via x402.
Pay-per-call MCP server. $0.03 USDC sends one transactional SMS to a US phone number via x402.
This MCP server is well-designed with appropriate security controls for its stated purpose of paid SMS delivery. Authentication is enforced via private key, permissions align with the use case (network calls to SMS service, environment variable for credentials), and code quality is solid. The primary concern is the reliance on user understanding of TCPA compliance—the server correctly delegates this responsibility to the operator via explicit attestation, but a user could misuse the tool despite clear warnings. Supply chain analysis found 2 known vulnerabilities in dependencies (0 critical, 2 high severity). Package verification found 1 issue.
4 files analyzed · 8 issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
This plugin requests these system permissions. Most are normal for its category.
Set these up before or after installing:
Environment variable: BUYER_PRIVATE_KEY
Add this to your MCP configuration file:
{
"mcpServers": {
"io-github-ultrastarz-x402-sms": {
"env": {
"BUYER_PRIVATE_KEY": "your-buyer-private-key-here"
},
"args": [
"-y",
"x402-sms-mcp"
],
"command": "npx"
}
}
}From the project's GitHub README.
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: Public beta on Base Sepolia (testnet). The seller's toll-free number is undergoing Twilio TFV approval (typically 3-5 business days from May 2026). During this window the payment flow works end-to-end on chain but Twilio will reject undelivered messages with code
30032. Once approved, messages will deliver and pricing flips to Base mainnet.
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.
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 verified toll-free number dispatches the SMS. Your private key never leaves your machine. The seller never sees it.
MIT
Be the first to review this server!
by Modelcontextprotocol · Developer Tools
Web content fetching and conversion for efficient LLM usage
by Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
by mcp-marketplace · Developer Tools
Create, build, and publish Python MCP servers to PyPI — conversationally.