mcpbeat Sign in

Rozo Checkout MCP Server

answering

Rozo Checkout is answering right now. Last checked 10 min ago. It exposes 10 tools. Last commit 30 Oct 2026.

Pay OpenRouter and Coinbase payment links with USDC, USDT, ETH, BNB, POL, SOL or BTC Lightning.

Uptime history 28 days of history · worst day 98%
28 days agonow
100.0%
Uptime 24h
91 of 91 checks
10
Tools
read from the server
77 ms
Response time
average over 24h
0
Stars
last commit 30 Oct 2026

What changed 36

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 5 October 2026. No other catalogue keeps this.

29 Oct 3 tool descriptions were rewritten payment_status, quote_invoice, supported_coins
29 Oct 2 tools changed the parameters they ask for create_deposit_order, quote_invoice
21 Oct 2 tool descriptions were rewritten quote_invoice, supported_coins
21 Oct 2 tools disappeared x402_sign, x402_topup
21 Oct a tool changed version
13 Oct 7 tool descriptions were rewritten10 times that day create_deposit_order, funding_capabilities, stellar_wallet_create_order and 4 more
13 Oct 6 tools appeared funding_capabilities, stellar_wallet_create_order, stellar_wallet_get_signing_request and 3 more
13 Oct a tool changed the parameters it asks for stellar_wallet_create_order
13 Oct a tool changed version
12 Oct 3 tool descriptions were rewritten create_deposit_order, quote_invoice, supported_coins
and 8 more, back to 5 October 2026

Tools have disappeared from this server

A tool that vanishes takes a piece of your agent with it, and the change arrives silently. Watch this server and every such change lands in your inbox.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 10 min ago.

run in your terminal
claude mcp add checkout --transport http 'https://mcp.rozo.ai/mcp?src=registry'
Settings → Connectors → Add custom connector, then paste this address
https://mcp.rozo.ai/mcp?src=registry
~/.codex/config.toml
[mcp_servers.checkout]
url = "https://mcp.rozo.ai/mcp?src=registry"
.cursor/mcp.json
{
  "mcpServers": {
    "checkout": {
      "url": "https://mcp.rozo.ai/mcp?src=registry"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "checkout": {
      "type": "http",
      "url": "https://mcp.rozo.ai/mcp?src=registry"
    }
  }
}

Available tools 10

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

stellar
stellar_wallet_create_order
Turn an approved quote into a payable order. Returns fundingId (keep it private: it is the only handle to the order), the one-time deposit address, the suggested amount and amountPolicy with minAcceptedAmount/maxPricedAmount when any_amount, payBefore and the accepted chains and tokens. orderId is your own reference: the server derives the upstream order id and Idempotency-Key from quoteId plus orderId, so it only has to be unique among your own orders. Retrying with the same quoteId and orderId returns the same order instead of a second one. Creates an order but moves no funds; an unpaid order expires at no cost. Fees come from the quote (fees and totals): never assume a fee. The receiving Stellar address signs ONE transaction (only when it is new or has no USDC trustline). The one-time deposit address is the same on Base, Ethereum, Arbitrum and Polygon; USDC or USDT is accepted 1:1. Follow deposit.amountPolicy: exact or missing means pay the EXACT deposit amount; any_amount uses the suggested amount and returned min/max bounds. Pay once, before payBefore. This server never holds keys: your own wallet pays and signs.
stellar_wallet_get_signing_request
When an order shows sign_stellar_onboarding, build the one transaction the receiving address must sign (creates the account if needed, adds the USDC trustline, claims the USDC, delivers XLM). Returns signingRequestId, the unsigned XDR, networkPassphrase, a readable operations list and expiresAt (at most 5 minutes). Sign it with the receiver wallet YOU control (Stellar SDK, Freighter, any wallet); do not modify it. Check the operations first, and decode the XDR locally to confirm it matches them exactly. The transaction source must NOT be your address (it is a ROZO channel account, so ROZO pays the network fee). Allowed, nothing else: ROZO-sourced beginSponsoringFutureReserves and createAccount for your address; from your address, changeTrust for USDC (issuer GA5ZSEJYB37JRC5AVCIA5MOP4RHTM335X2KGX3IHOJAPP5RE34K4KZVN), endSponsoringFutureReserves, claimClaimableBalance, and at most one payment: the sponsor fee in USDC to ROZO claim custody GBLTI2TTQXUAYNKGCQ63YA55KTFEAOQJ3DPBPELNPWCJVE76ADWMXUAE; and a ROZO-sourced XLM payment to your address. Any other operation type or source (setOptions, extra payments): refuse. Amounts: the claimed USDC (gross) equals the current stable leg minimumAmount (order.legs, after repricing) plus the sponsor fee; the sponsor fee is fixed at quote time (0.0000001 USDC with a paid usdGas tier, the quoted stellar_sponsor_fee with usdGas "0", no fee payment if the address needed no onboarding); the XLM payment equals the native (XLM) leg minimumAmount. The XDR shows only the claimable balance id; its amount is in the operations list and on Horizon /claimable_balances/{id}. The hash of the locally decoded transaction (tx.hash() as hex) must equal the txHash of this signing request. Every ROZO-sourced operation and the transaction source must be one of funding_capabilities rozoAccounts (reserveSponsor, xlmPayer, transactionSources). Do not echo fundingId into logs. Expired, or submit failed: just call this tool again; it supersedes the old request and returns a fresh XDR (only refused while a signed one is still submitting). This server never sees your key. Then call stellar_wallet_submit_signed.
stellar_wallet_order_status
Read a funding order by fundingId: status, pendingActions (sign_stellar_onboarding means the receiver must sign), the deposit, and each leg (USDC, XLM) with its own status, delivered amount and tx hash. Read-only. Poll about every 15 seconds; completed only when every leg is confirmed.
stellar_wallet_quote
Price sending USDC/USDT from Base, Ethereum, Arbitrum or Polygon to USDC on a Stellar address. If the address is new or has no USDC trustline, the same plan opens the account, adds the trustline and (with usdGas) gives XLM, in one transaction the address signs once. Returns quoteId and planDigest (needed by stellar_wallet_create_order), the USDC and XLM amounts the receiver gets, every fee line and totals, and whether a signature will be needed. Valid about 10 minutes. Read-only: no deposit address, nothing reserved. usdGas: "0" no XLM, "0.5" or "1" buys XLM (see funding_capabilities for amounts); omitted = the server default. Fees come from the quote (fees and totals): never assume a fee. The receiving Stellar address signs ONE transaction (only when it is new or has no USDC trustline). The one-time deposit address is the same on Base, Ethereum, Arbitrum and Polygon; USDC or USDT is accepted 1:1. Follow deposit.amountPolicy: exact or missing means pay the EXACT deposit amount; any_amount uses the suggested amount and returned min/max bounds. Pay once, before payBefore. This server never holds keys: your own wallet pays and signs.
stellar_wallet_submit_signed
Submit the XDR your own wallet signed for a signing request. This is the claim: the account, trustline, USDC and XLM land in that one transaction. Submitting the same signed XDR again is safe (idempotent). Accepts only the signed transaction envelope, never a secret key. "submitted" is not delivery: poll stellar_wallet_order_status until completed. If it answers template_expired or failed, call stellar_wallet_get_signing_request again and sign the new XDR.
deposit
create_deposit_order
Creates a one-time deposit order; you pay from your own wallet. Returns the deposit address (or Lightning invoice), the exact amount to send (also in base units with the token decimals), 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. For a native coin the result also carries quoteExpiresAt (the end of the price lock, which expiresAt equals): send the exact coin amount before it. Native coins (ETH on Ethereum, Base, Arbitrum; BNB on BNB Chain; POL on Polygon; SOL on Solana) are exact-out like Lightning: the order states the exact coin amount, priced at the current rate plus an FX spread on top of the service fee, and that price holds only until quoteExpiresAt. Native orders are capped at $3500 per invoice (native ETH on Ethereum needs at least $1), and a native coin is offered only when quote_invoice lists it for that invoice. ZEC on Zcash (Beta) is not available through this server: send a payer holding ZEC to https://checkout.rozo.ai/zec.
funding
funding_capabilities
What the keyless ROZO Funding API supports right now: whether stellar_onboarding is on, the source chains and USDC assets, the Stellar USDC output, the usdGas options (XLM amounts) and per-order limits. Read-only, creates nothing. Fees come from the quote (fees and totals): never assume a fee. The receiving Stellar address signs ONE transaction (only when it is new or has no USDC trustline). The one-time deposit address is the same on Base, Ethereum, Arbitrum and Polygon; USDC or USDT is accepted 1:1. Follow deposit.amountPolicy: exact or missing means pay the EXACT deposit amount; any_amount uses the suggested amount and returned min/max bounds. Pay once, before payBefore. This server never holds keys: your own wallet pays and signs.
payment
payment_status
Check a Rozo order by rozoPaymentId: whether the deposit arrived, bridging/payout progress, and whether the OpenRouter or other AI service invoice settled. Read-only.
quote
quote_invoice
Answers what a specific OpenRouter top-up or other AI service invoice charges, whether it can still be paid through Rozo Checkout, and which coins can pay it. Takes the payment link URL and returns the merchant, invoice amount, callerPays (the USD amount the invoice charges), the link expiry, payability and supportedSources: the coins THIS invoice can be paid with. The exact amount to send in a given coin, including the service fee, bridge and network fees, or the FX spread on a native coin, comes from create_deposit_order. Offer a native coin (ETH, BNB, POL, SOL) only when it appears in supportedSources. Creates nothing and moves no funds.
supported
supported_coins
Answers which cryptocurrencies and chains can pay an OpenRouter credit top-up or another AI service invoice through Rozo Checkout: USDC and USDT on Ethereum, BNB Chain, Polygon, Arbitrum and Solana; USDC on Base and Stellar; native ETH (Ethereum, Base, Arbitrum), BNB, POL and SOL; BTC over Lightning. Returns each chain id, token symbol and token decimals. Static list, needs no payment link and makes no network call; quote_invoice reports which of these a specific invoice accepts. Native coins (ETH on Ethereum, Base, Arbitrum; BNB on BNB Chain; POL on Polygon; SOL on Solana) are exact-out like Lightning: the order states the exact coin amount, priced at the current rate plus an FX spread on top of the service fee, and that price holds only until quoteExpiresAt. Native orders are capped at $3500 per invoice (native ETH on Ethereum needs at least $1), and a native coin is offered only when quote_invoice lists it for that invoice. ZEC on Zcash (Beta) is not available through this server: send a payer holding ZEC to https://checkout.rozo.ai/zec.

Tools removed

Tools this server used to expose. Anything built against them stopped working on the day they went.

x402_sign
removed 21 Oct 2026
x402_topup
removed 21 Oct 2026

Endpoints

URLTransportStateLatencyChecked
https://mcp.rozo.ai/mcp?src=registry streamable-http answering 63 ms 10 min ago

Alternatives to Rozo Checkout

same job, measured the same way
send21
by send21io

Crypto pay links and API for people and AI agents. BTC, Lightning, USDC, USDT, EURC, SOL, ETH.

14 tools answering
MCP Coinbase Commerce
by codespar

MCP server for Coinbase Commerce — crypto merchant payments (BTC/ETH/USDC); settle crypto or fiat

62 installs/wk local only
Toreador
by toreador

Generate crypto QR codes (BTC, ETH, SOL, USDC, USDT, EURC) and manage payment sessions.

66 installs/wk local only
Quay
by quay21

Pay-per-call TRON fee, payment, and address checks. Agents pay USDT or USDC.

4 tools answering
Cabin Flights
by kobuta23

Search and book real flights with USDC on Base. 500+ airlines, crypto-native payments.

38 installs/wk local only
AgnicPay
by agnicpay-prog

X402 payment MCP for AI agents. Auto-pay 300+ APIs with USDC on Base and Solana.

answering
GotSOL.app
by gotsol

USDC wallets, payment links and x402 payments on Solana for AI agents.

13 tools answering
Qashier MCP by usefulapi
by usefulapi

Read checkout sessions; create payment links, expire sessions and refund payments in Qashier.

5 tools answering

Rozo Checkout — questions

Answers built from our own checks of this server.

What can Rozo Checkout do?
It exposes 10 tools, read directly from the server on our last check. Among them: create_deposit_order, funding_capabilities, payment_status, quote_invoice, stellar_wallet_create_order, stellar_wallet_get_signing_request and 4 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Rozo Checkout working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 77 ms. The bar chart above shows every period we have measured.
Did Rozo Checkout ever remove tools?
Yes. x402_sign, x402_topup are no longer exposed — we recorded the date each one disappeared. A tool vanishing usually means a breaking change for anything that depended on it.
How do I connect Rozo Checkout?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Rozo Checkout need an API key?
No. Rozo Checkout completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 10 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Rozo Checkout?
It answers our handshake in 77 ms on average, which is faster than 97% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Rozo Checkout open source?
We cannot say either way: written in TypeScript and 0 stars on GitHub, but we could not determine the licence, and without one the code is not open source by default.