Rozo Checkout MCP Server

rozo-checkout-mcp

A small remote MCP server that lets an AI agent help a user pay an OpenRouter top-up (a Coinbase payment link, payments.coinbase.com/payment-links/pl_* or payment-sessions/paymentSession_*) with the coin they already hold:

• USDC or USDT on Solana, BNB Chain, Ethereum, Polygon
• USDC on Base or Stellar
• BTC over Lightning

It runs as a Cloudflare Worker and speaks MCP streamable HTTP at /mcp.

It never custodies funds

This server holds no private keys, signs nothing and sends nothing. It only:

1. reads a quote for the Coinbase link,
2. asks Rozo (through MPP Router) for a one-time deposit order, and
3. reads order status.

The user pays from their own wallet. An order that is never funded expires and costs nothing. There are no secrets, no auth and no stored state; each request is handled statelessly.

Tools

create_deposit_order applies the same guards as the CLI before it returns a deposit address: link payability (not used, not expired, v3 session still CREATED), an existing order must be payment_unpaid with no pay-in and the same coin, the address must not be on the compromised-address list, and at least 10 minutes must remain on both the order and the link.

Upstream endpoints (identical request shapes to the CLI, all keyless):

• POST https://apiserver.mpprouter.dev/v1/services/rozo-agent-api/quote-invoice
• POST https://apiserver.mpprouter.dev/v1/services/rozo-agent-api/create-invoice
• GET https://apiserver.mpprouter.dev/v1/services/rozo-agent-api/invoice-status?rozo_payment_id=...
• GET https://intentapiv4.rozo.ai/functions/v1/payment-api/payments/<uuid> (read-only)

Channel attribution: ?src=

Every create-invoice call carries

{ "client": "rozo-checkout-mcp/<version>",
  "attribution": { "client": "rozo-checkout-mcp/<version>", "utm_source": "<src>" } }

<src> comes from the src query parameter of the MCP URL the client connected to. It is lowercased, limited to [a-z0-9._-] and 100 characters, and defaults to mcp. Give each channel its own URL so orders can be split by channel:

Connect

Claude Desktop / Claude.ai

Settings, Connectors, Add custom connector, URL https://mcp.rozo.ai/mcp?src=claude.

For a local claude_desktop_config.json through the mcp-remote bridge:

{
  "mcpServers": {
    "rozo-checkout": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.rozo.ai/mcp?src=claude-desktop"]
    }
  }
}

Claude Code

claude mcp add --transport http rozo-checkout "https://mcp.rozo.ai/mcp?src=claude-code"

Cursor

~/.cursor/mcp.json:

{ "mcpServers": { "rozo-checkout": { "url": "https://mcp.rozo.ai/mcp?src=cursor" } } }

MCP Inspector

npx @modelcontextprotocol/inspector
# Transport: Streamable HTTP, URL: http://127.0.0.1:8787/mcp?src=inspector (local) or the prod URL

Develop

npm install
npm test            # vitest
npm run typecheck
npx wrangler dev    # http://127.0.0.1:8787/healthz and /mcp

Raw handshake with curl:

curl -s -X POST 'http://127.0.0.1:8787/mcp?src=dev' \
  -H 'Content-Type: application/json' -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"curl","version":"0"}}}'
curl -s -X POST 'http://127.0.0.1:8787/mcp?src=dev' \
  -H 'Content-Type: application/json' -H 'Accept: application/json, text/event-stream' \
  -H 'MCP-Protocol-Version: 2025-06-18' \
  -d '{"jsonrpc":"2.0","id":2,"method":"tools/list"}'

Deploy

Deployment and the mcp.rozo.ai custom domain need owner approval and are not automated here. wrangler.toml pins the Cloudflare account that owns the rozo.ai zone and keeps the custom domain route commented out until then.

MCP registry

server.json describes this server for the official MCP registry as io.github.RozoAI/checkout, with the remote https://mcp.rozo.ai/mcp?src=registry. Publishing under the ai.rozo namespace requires proving control of rozo.ai (DNS or HTTP verification with mcp-publisher).