rozo-checkout-mcp
Registry code: 4bb3c9581e967203
Pay an OpenRouter (Coinbase payment link) top-up with USDC/USDT on Solana, BNB Chain, Ethereum, Polygon, Base, Stellar, or BTC over Lightning. Flow: quote_invoice -> create_deposit_order -> the user sends from their own wallet -> payment_status. This server never holds keys or funds. x402 APIs: x402_topup funds a prepaid Rozo balance with USDC or USDT only (native coins and Lightning are for create_deposit_order); x402_sign returns a PAYMENT-SIGNATURE for one 402 requirement (USDC on Base or Solana only). You make the paid HTTP request yourself.
- endpoint
- https://mcp.rozo.ai/mcp?src=registry
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is rozo-checkout-mcp live?
- Yes — it answered the hub's last check (checked 21m ago). It answered 100% of checks over the last 30 days.
- Is rozo-checkout-mcp free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does rozo-checkout-mcp have?
- 6 tools: create_deposit_order, payment_status, x402_topup, x402_sign, quote_invoice, supported_coins.
- Is rozo-checkout-mcp safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 99.5%· all time 99.5%
last good check
of 6 tools
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- live → degraded· timeout after 20000ms
- down → live
- used for
- pay an openrouter top-up invoice with stablecoins
- create a crypto deposit order
- check payment status
- list supported coins
- takes → gives
- text, data → data
- tools
- 3 reads1 moves money
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
supported_coins reads open 18h ago
List the coins and chains you can pay an OpenRouter (Coinbase) invoice with through Rozo. Static list, no network call.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": {} }arguments 5 linescreate_deposit_order moves money unknown never probed
Creates a one-time deposit order; you pay from your own wallet. Returns the deposit address (or Lightning invoice), the exact amount to send, any required memo, the expiry and the rozoPaymentId. This server holds no keys and sends nothing. Send exactly the amount, on exactly that chain and token, before expiresAt. An unfunded order simply expires at no cost.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "url", "chainId", "tokenSymbol" ], "properties": { "url": { "type": "string", "maxLength": 512, "description": "Coinbase link: https://payments.coinbase.com/payment-links/pl_... or https://payments.coinbase.com/payment-sessions/paymentSession_..." }, "email": { "type": "string", "maxLength": 320, "description": "Optional contact email so ROZO can reach the payer if the payment needs attention. Ask the user once if they are present; never required, omit it if they decline." }, "chainId": { "enum": [ "1", "56", "137", "900", "1500", "8453", "lightning" ], "type": "string", "description": "Source chain id from supported_coins, e.g. \"900\" (Solana), \"8453\" (Base), \"lightning\"." }, "tokenSymbol": { "type": "string", "maxLength": 8, "minLength": 2, "description": "Token you will pay with, e.g. USDC, USDT, BTC." } } }arguments 40 linespayment_status reads unknown never probed
Check a Rozo order by rozoPaymentId: whether the deposit arrived, bridging/payout progress, and whether the Coinbase invoice settled. Read-only.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "rozoPaymentId" ], "properties": { "rozoPaymentId": { "type": "string", "maxLength": 64, "description": "Order UUID returned by create_deposit_order." } } }arguments 14 linesx402_topup unknown never probed
Fund a prepaid Rozo x402 balance with USDC or USDT, through a one-time deposit address you pay from your own wallet. Same fields as POST /v1/x402/topup: amount (USD), token, chain. Topup coins: USDC/USDT on Ethereum, BNB Chain, Polygon, Solana, Arbitrum; USDC on Base, Stellar. Native coins (ETH, BNB, SOL, ...) and BTC/Lightning are not accepted for top ups. Holding a native coin or sats? Use create_deposit_order / ROZO Checkout to top up OpenRouter instead. The x402 payment leg is USDC on Base (eip155:8453) only, scheme "exact"; Solana payment leg is coming later. USDT can fund the balance (x402_topup) but never pays a seller directly. Without an agent key, one is created and returned ONCE in this result: store it, it owns the balance. Minimum $5.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "amount", "token", "chain" ], "properties": { "chain": { "enum": [ "1", "56", "137", "900", "1500", "8453", "42161" ], "type": "string", "description": "Chain id: \"1\" Ethereum, \"56\" BNB Chain, \"137\" Polygon, \"900\" Solana, \"42161\" Arbitrum, \"8453\" Base, \"1500\" Stellar." }, "token": { "type": "string", "maxLength": 8, "minLength": 2, "description": "Coin you will send: USDC or USDT (USDT not on Base or Stellar)." }, "amount": { "type": "string", "maxLength": 16, "description": "USD amount to credit, e.g. \"20\". Minimum 5." }, "agentKey": { "type": "string", "maxLength": 220, "description": "Agent key (ak_...). Prefer setting it once as \"Authorization: Bearer ak_...\" on the MCP connection; this argument overrides that. Never share it." } } }arguments 40 linesx402_sign unknown never probed
Pay an x402 endpoint from the prepaid Rozo balance. You make the HTTP request yourself; when it answers 402, pass the payment requirement you chose from its "accepts" list here. Returns the value to send in the PAYMENT-SIGNATURE header (x402 v1: X-PAYMENT); replay the same request with it. Same fields as POST /v1/x402/sign: accepts, budget, idempotencyKey. The x402 payment leg is USDC on Base (eip155:8453) only, scheme "exact"; Solana payment leg is coming later. USDT can fund the balance (x402_topup) but never pays a seller directly. Generate one idempotencyKey (UUID) per payment and reuse it on every retry: the same key returns the same signature instead of charging twice. Never send Rozo your request body, headers or the seller API keys; only the accepts entry. A 503 (other than X402_RETRY) means the x402 payer is not enabled for this key; nothing was charged.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "accepts", "budget", "idempotencyKey" ], "properties": { "budget": { "type": "string", "maxLength": 16, "description": "Most this one payment may cost, in USD, e.g. \"0.50\". Rozo refuses to sign above it." }, "accepts": { "type": "array", "items": { "type": "object", "propertyNames": { "type": "string" }, "additionalProperties": {} }, "maxItems": 8, "minItems": 1, "description": "Payment requirement(s) copied verbatim from the 402 challenge \"accepts\" list. Pass the one you chose." }, "agentKey": { "type": "string", "maxLength": 220, "description": "Agent key (ak_...). Prefer setting it once as \"Authorization: Bearer ak_...\" on the MCP connection; this argument overrides that. Never share it." }, "resource": { "type": "object", "description": "The \"resource\" object from the challenge, if present.", "propertyNames": { "type": "string" }, "additionalProperties": {} }, "x402Version": { "type": "integer", "maximum": 9, "minimum": 1, "description": "x402Version from the challenge (2 if it came in the PAYMENT-REQUIRED header)." }, "idempotencyKey": { "type": "string", "maxLength": 64, "description": "UUID you generate once per payment and reuse on retries." } } }arguments 53 linesquote_invoice reads unknown 18h ago
Look up a Coinbase payment link (e.g. an OpenRouter top-up) and return the merchant, invoice amount, what the payer pays, the link expiry and whether it is still payable. Creates nothing and moves no funds.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "url" ], "properties": { "url": { "type": "string", "maxLength": 512, "description": "Coinbase link: https://payments.coinbase.com/payment-links/pl_... or https://payments.coinbase.com/payment-sessions/paymentSession_..." } } }arguments 14 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id4bb3c9581e967203.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/4bb3c9581e967203/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/4bb3c9581e967203?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.