X402 Sms

io.github.UltraStarz由 GitHub 账号 UltraStarz 发布v0.1.0更新于 Oct 24, 2026

Pay-per-call MCP server. $0.03 USDC sends one transactional SMS to a US phone number via x402.

已验证STDIO仅桌面金融沟通与协作

概览

AI 生成的概览

让助手向美国手机号发送事务性短信,并从配置的钱包按条支付 USDC 费用。

可以做什么
提供 send_sms 工具,通过第三方卖家的免费电话号码向美国(+1 E.164)号码发送事务性短信。每次调用花费 0.03 USDC,通过 x402 从配置的买家钱包自动签名支付,并返回 Twilio SID 和链上结算哈希。若短信正文缺少退订说明,服务器会自动追加;同时区分待审批、限流和 Twilio 拒绝等不同错误形态。
适用场景
适合助手需要以短信通知已同意的美国接收者的场景,例如告知某人长时间任务已完成。适用于一次性事务性通知,而非营销、群发或非美国号码的短信。
运行要求
通过 npx(Node.js)以 stdio MCP 服务器在本地运行,仅支持桌面客户端。需要 BUYER_PRIVATE_KEY,即 Base Sepolia 上钱包的以太坊私钥,钱包需有少量 ETH 作 gas 和 USDC 用于支付。SMS_URL 可选,默认指向卖家的公开端点。需要网络访问。
安装前请注意
BUYER_PRIVATE_KEY 是可用于花钱的钱包私钥,请使用一次性充值钱包,并避免放入共享配置。每次调用花费 0.03 USDC,即使 Twilio 侧拒绝也算一次发送尝试。运营者须按 TCPA 规则确保接收者已同意;禁止营销、未同意、非美国及受限内容的短信。短信内容和支付信息会发送给第三方卖家,发送记录会被留存用于审计。

安装

在 SourceWeft 中

  1. 打开 控制台中的 X402 Sms,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照 仓库 中的启动说明。

README

x402-sms-mcp

A paid MCP server that lets AI agents send SMS messages to US phone numbers.

Each send_sms tool call:

  1. Sends a transactional SMS via the seller's toll-free number (Twilio verification in progress)
  2. Auto-appends Reply STOP to opt out if the body doesn't include opt-out language
  3. Costs $0.03 USDC per message, paid automatically from the configured wallet via x402

No 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 /send calls short-circuit to a 503 delivery_pending_tfv_approval response 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.

Install in Claude Desktop / Cursor / Windsurf

Add this to your MCP config (~/Library/Application Support/Claude/claude_desktop_config.json on macOS):

json
{  "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.

What you need

A wallet on Base Sepolia (testnet) funded with:

Generate a throwaway key:

bash
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.

Try it

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.

Compliance — please read

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:

  • Send marketing or promotional content
  • Text strangers, scraped lists, or anyone who hasn't opted in
  • Send to non-US numbers (the seller currently rejects non-+1 E.164)
  • Send anything related to S.H.A.F.T.-C (Sex, Hate, Alcohol, Firearms, Tobacco, Cannabis)

The seller-side automatically:

  • Appends Reply STOP to opt out to every message
  • Honors carrier-level STOP/HELP keyword handling
  • Logs each send for audit purposes

If you have any doubt about consent, do not call this tool.

Configuration

Env varRequiredDefault
BUYER_PRIVATE_KEYyes—
SMS_URLnohttps://x402-sms-server-production.up.railway.app/send

To point the MCP server at your own seller deployment, override SMS_URL.

Errors you might see

The MCP surfaces three distinct error shapes so the model can explain what happened to the user and decide whether to retry.

CauseWhat you'll see in chatWas 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 guidanceno
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_secondsno
Twilio-side rejection (e.g. invalid number 21211, opted-out 21610)Friendly hint mapped from the Twilio error code + the full response bodyyes (the send tried)

For the full mapping of Twilio error codes the MCP recognizes, see TWILIO_HINTS in src/index.ts.

How it works

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.

Roadmap

  • Now (2026-05-22): Base Sepolia testnet, TFV pending. Payment flow verified end-to-end; deliveries gated on Twilio approval.
  • Once TFV clears: Real US SMS delivery, testnet pricing held while we collect early traffic.
  • A few weeks out: A2P 10DLC Brand approval → higher per-day throughput tier.
  • Mainnet flip: Production launch, USDC settles on Base mainnet; Solana facilitator on roadmap after.

License

MIT

来源:README.md,提交 61115a4

工具

0
SourceWeft 尚未在沙箱中启动过该软件包,因此其工具未知。

版本历史

1
  1. v0.1.0最新Sep 16, 2026

评分

已满足适用检查项的 40%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通25 分

    请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。

  • 已声明认证方式10 分

    请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。

  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分

    请在仓库或注册中心条目中声明许可证。