ripio-community-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RIPIO_API_KEY | Yes | Your Ripio API key | |
| RIPIO_TRADE_RPS | No | Ripio Trade requests per second. Default 1; up to 3.5 if your account has verified documents | 1 |
| RIPIO_API_SECRET | Yes | Your Ripio secret key |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ripio_get_portfolioA | What the user holds on Ripio right now: Wallet (fiat and crypto), memecoins and Ripio Trade balances in one list, with available and locked amounts and an estimated value in ARS and USD at Ripio app sell rates. Zero balances are hidden unless include_zero is true. |
| ripio_list_activityA | Deposits, withdrawals and swaps (source "wallet", default) or Ripio Trade statement entries (source "trade"), newest first, in one normalized shape. Card transactions, in-app buys/sells and bill payments are not available from Ripio's API. Pass next_cursor back as cursor for older items. Dates are UTC; on Wallet, from/to filter the returned page only; on Ripio Trade a from/to range can span up to 182 days. |
| ripio_get_transactionA | Full detail of one Wallet movement by its id (from ripio_list_activity with source "wallet"): amounts, fee, rail, counterparty, status and the on-chain hash when there is one. |
| ripio_get_pricesA | Current prices for one or more assets: the Ripio app buy/sell rates (with spread) and, when the pair exists, the Ripio Trade book (bid, ask, last, 24h change and volume), so app and exchange prices can be compared. |
| ripio_estimate_tradeA | Estimates what a market order on Ripio Trade would cost or return right now: unit price for that size, gross value, your taker fee and the total. Read-only: nothing is executed. |
| ripio_get_limitsA | How much the account can still deposit, withdraw or swap: Ripio limits per rail (bank, pix, crypto, ripio and the account-wide limit) with daily, monthly and annual caps and what remains, plus the operations and fees of each rail. |
| ripio_list_open_ordersA | Open orders on Ripio Trade, optionally for one pair or side, with price and requested, executed and remaining amounts. |
| ripio_get_deposit_addressA | The Ripio app (Wallet) crypto deposit address for an asset on one network, with its memo/tag when the network needs one and the warnings to relay before anyone sends funds. Without a network, or with an ambiguous one, it returns no address and lists the networks that receive the asset. It never creates an address. Ripio Trade uses different addresses. |
| ripio_verify_deposit_addressA | Checks with code, character by character, that an address (and memo/tag) someone is about to send to is exactly one of the account's Ripio app (Wallet) deposit addresses, on a network that credits the asset, and flags mistyped copies. Pass the address as pasted from where it will actually be used, plus the asset and network the sender will use. Ripio Trade addresses are not checked. |
| ripio_get_deposit_accountsA | The account's Ripio bank-deposit accounts for fiat: the CVU and alias in Argentina (PIX in Brazil), with the rules to relay before anyone transfers. Crypto deposits use ripio_get_deposit_address instead. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 10 tools
Each tool targets a distinct action or resource: activity listing, transaction detail, deposit addresses (crypto vs fiat), address verification, trade estimation, limits, portfolio, prices, and open orders. There is no overlap; even the two deposit-related tools are clearly separated by asset type. Agents should have no trouble selecting the correct tool for a given query.
All tool names follow a uniform `ripio_` prefix with a verb-noun structure (list_activity, get_transaction, get_deposit_address, verify_deposit_address, estimate_trade, list_open_orders). The pattern is consistent and predictable, using snake_case throughout. This makes the tool surface easy to navigate programmatically.
With 10 tools, the server is well-scoped for a community/account information and read-only trading context. Each tool addresses a specific need without redundancy, and the count is within the ideal range of 3–15. No tool feels unnecessary, and there is no indication of bloat or sparseness.
The tool surface covers the primary read-only operations: viewing activity, transaction details, deposit addresses, portfolio, prices, limits, and open orders. It lacks direct tools for executing trades or withdrawals, but the descriptions indicate the server is intentionally read-only (e.g., 'Read-only: nothing is executed', 'It never creates an address'). Minor gaps exist (e.g., no explicit tool for account or KYC info), but they are not critical for the stated purpose.