Skip to main content
Glama

Server Details

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

If you are the author of this connector, you can claim ownership. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
Repository
RozoAI/rozo-checkout-mcp
GitHub Stars
0
ChatGPT
–
Claude
–

TDQS

A4.1/5.0

Scored across 10 tools

Disambiguation4/5

Each tool has a distinct role, and the descriptions clearly separate the two flows: the general invoice path (quote_invoice → create_deposit_order → payment_status) and the Stellar funding path (stellar_wallet_quote → stellar_wallet_create_order → stellar_wallet_get_signing_request → stellar_wallet_submit_signed → stellar_wallet_order_status). The remaining risk is that the two order-creation tools and the two status tools look interchangeable at a glance and are only distinguished by subtle input handles (invoice URL/rozoPaymentId vs quoteId+planDigest/fundingId).

Naming Consistency4/5

Names are consistently snake_case and the stellar_wallet_ prefix cleanly namespaces the Stellar sub-flow. Minor deviations exist: several tools are noun phrases (payment_status, quote_invoice, funding_capabilities, supported_coins) while others are verb_noun (create_deposit_order, stellar_wallet_submit_signed), so the verb convention is not uniform across the set.

Tool Count4/5

Ten tools is a good size for the scope and every tool maps to a real step (quote, create, sign, submit, status, capabilities, coin list). The only waste is that the two parallel flows duplicate the create/quote/status roles, so a couple of tools feel like siblings rather than distinct capabilities.

Completeness4/5

The primary lifecycles are covered end-to-end, including read-only preflight (supported_coins, funding_capabilities, quote_invoice) and post-payment tracking. Minor gaps: no explicit cancel/abandon or list/history operation, and no generic lookup for orders that lack both rozoPaymentId and url, though an unfunded order simply expiring makes these low-impact.

Available Tools

10 tools
create_deposit_orderCreate a deposit orderAInspect

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. For TRON or TON the result carries the receiving address, the exact amount, the TON comment when one is required, the fees and expiresAt, and no rozoPaymentId: track it with payment_status and the url. 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 ETH, BNB and SOL take OpenRouter invoices of up to 10,000 credits (about $10,500; refused only above $12750 of callerPays, service fee included, so a 10,000-credit invoice always fits). POL is capped at $3500 (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 is not available through this server: send a payer holding ZEC to https://checkout.rozo.ai/zec. On-chain BTC (the Bitcoin network, Beta) is not available through this server either; the lightning chain id here is Bitcoin Lightning only. Send a payer who wants to pay on-chain to https://checkout.rozo.ai/btc-onchain. USDT and TRX on TRON (Beta) and USDT on TON go through a dedicated route (route "tron_ton_alpha", the same backend as checkout.rozo.ai/tron and /ton): create_deposit_order returns one exact amount, a receiving address and, on TON when required, a six digit comment, valid until expiresAt. TRON Beta charges 1% with a $0.30 minimum; TON charges 1%; the exact fees come with the order. These orders have no rozoPaymentId: check them with payment_status and the payment link url. Availability can change; quote_invoice reports whether TRON and TON are open for a given invoice.

Inputs: url (required), chainId (required), tokenSymbol (required), email.

funding_capabilitiesStellar wallet funding capabilitiesA
Read-onlyIdempotent
Inspect

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.

Inputs: no named parameters.

payment_statusPayment statusA
Read-onlyIdempotent
Inspect

Check a Rozo order: whether the deposit arrived, bridging/payout progress, and whether the OpenRouter or other AI service invoice settled. Pass rozoPaymentId for orders that have one, or url (the payment link) for TRON / TON orders, which have none. Read-only.

Inputs: url, rozoPaymentId.

quote_invoiceQuote an AI service invoiceA
Read-onlyIdempotent
Inspect

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 total USD charged: invoice plus the Rozo service fee; also callerPaysAtomicUsdc in 6-decimal units), the breakdown original (invoice face value), serviceFee and feeBps (fee rate in basis points, 100 = 1%), the link expiry, payability and supportedSources: the coins THIS invoice can be paid with. The exact amount to send in a given coin, which adds bridge and network fees, or the FX spread on a native coin, on top of callerPays, 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.

Inputs: url (required).

stellar_wallet_create_orderCreate a Stellar wallet funding orderA
Idempotent
Inspect

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.

Inputs: orderId (required), quoteId (required), planDigest (required).

stellar_wallet_get_signing_requestGet the Stellar transaction to signAInspect

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.

Inputs: fundingId (required), walletAddress (required).

stellar_wallet_order_statusStellar wallet funding order statusA
Read-onlyIdempotent
Inspect

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.

Inputs: fundingId (required).

stellar_wallet_quoteQuote: fund a Stellar walletA
Read-only
Inspect

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.

Inputs: amountUsd (required), sourceChain (required), receiverAddress (required), usdGas.

stellar_wallet_submit_signedSubmit the signed Stellar transactionA
Idempotent
Inspect

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.

Inputs: signedXdr (required), signingRequestId (required).

supported_coinsSupported coinsA
Read-onlyIdempotent
Inspect

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; USDT and TRX on TRON (Beta), USDT on TON. Returns each chain id, token symbol and token decimals (TRON and TON rows carry route "tron_ton_alpha", a beta flag and their fee wording), plus webOnlyRoutes: coins served only on checkout.rozo.ai pages. 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 ETH, BNB and SOL take OpenRouter invoices of up to 10,000 credits (about $10,500; refused only above $12750 of callerPays, service fee included, so a 10,000-credit invoice always fits). POL is capped at $3500 (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 is not available through this server: send a payer holding ZEC to https://checkout.rozo.ai/zec. On-chain BTC (the Bitcoin network, Beta) is not available through this server either; the lightning chain id here is Bitcoin Lightning only. Send a payer who wants to pay on-chain to https://checkout.rozo.ai/btc-onchain. USDT and TRX on TRON (Beta) and USDT on TON go through a dedicated route (route "tron_ton_alpha", the same backend as checkout.rozo.ai/tron and /ton): create_deposit_order returns one exact amount, a receiving address and, on TON when required, a six digit comment, valid until expiresAt. TRON Beta charges 1% with a $0.30 minimum; TON charges 1%; the exact fees come with the order. These orders have no rozoPaymentId: check them with payment_status and the payment link url. Availability can change; quote_invoice reports whether TRON and TON are open for a given invoice.

Inputs: no named parameters.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Non-custodial multi-chain crypto payment gateway via CoinVoyage. 15 tools for creating PayOrders, managing webhooks, and cross-chain swaps. Supports BTC, SOL, ETH, Base, Arbitrum, Polygon, BSC, Sui, USDC/USDT.
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Connects Claude Desktop, Cursor, or any MCP-compatible client to 36+ frontier LLMs with automatic per-token payments in USDC on Solana.
      5
      MIT
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.