Ripio (community, read-only)
NPM · RIPIO-COMMUNITY-MCP · SCANNED SEP 26
Unofficial, read-only MCP server for your Ripio account: balances, activity, prices and deposits.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 0 of 4 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to ruizemanuel/ripio-community-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability73
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1292 tokens (~129/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage95
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 84% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
How do I install the Ripio (community, read-only) MCP server?
Ripio (community, read-only) runs locally as an npm package, launched with npx -y ripio-community-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · ripio-community-mcp
claude mcp add ruizemanuel-ripio-community-mcp -- npx -y ripio-community-mcp
{
"mcpServers": {
"ruizemanuel-ripio-community-mcp": {
"command": "npx",
"args": [
"-y",
"ripio-community-mcp"
]
}
}
} {
"servers": {
"ruizemanuel-ripio-community-mcp": {
"command": "npx",
"args": [
"-y",
"ripio-community-mcp"
]
}
}
} codex mcp add ruizemanuel-ripio-community-mcp -- npx -y ripio-community-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ruizemanuel-ripio-community-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"ripio-community-mcp"
],
"enabled": true
}
}
} openclaw mcp add ruizemanuel-ripio-community-mcp --command npx --arg -y --arg ripio-community-mcp
mcp_servers:
ruizemanuel-ripio-community-mcp:
command: "npx"
args: ["-y", "ripio-community-mcp"] {
"McpServers": {
"ruizemanuel-ripio-community-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"ripio-community-mcp"
]
}
}
} assistant mcp add ruizemanuel-ripio-community-mcp -t stdio -c npx -a -y ripio-community-mcp
{
"mcpServers": {
"ruizemanuel-ripio-community-mcp": {
"command": "npx",
"args": [
"-y",
"ripio-community-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 26 Sept 26 +11
- Known CVEs: unverified → pass ▲ security
- Dependency health: unverified → 1.00 ▲ functional
- 25 Sept 26 70
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 26 Sept 2026 · Analysed npm/ripio-community-mcp@0.2.3
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | ruizemanuel/ripio-community-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/ruizemanuel/ripio-community-mcp/.github/workflows/release.yml@refs/tags/v0.2.3 |
| Rekor log index | 2961778379 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:fcf00b62fe373c6d2bd100e92ad5d8ab413688f0f31c79c42a5e035f71c2ef89ab88819ab62287c44b44172ee5920bb85df2df54d62e0ece62cd967d2 |
Background: How many MCP packages publish verified provenance →
Dependencies 4 packages
| Packages resolved | 4 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
ripio_estimate_trade Estimate a Ripio Trade order ~107
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.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | yes | Amount in the base currency, e.g. "100" to buy 100 USDT on USDT_ARS. |
| pair | string | yes | Ripio Trade pair, e.g. USDT_ARS. |
| side | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | yes | – |
| estimated_fee | string | – | – |
| estimated_total | string | yes | – |
| estimated_unit_price | string | yes | – |
| gross_value | string | yes | – |
| note | string | yes | – |
| pair | string | yes | – |
| side | string | yes | – |
| taker_fee_pct | string | – | – |
| warnings | array | yes | – |
No examples provided.
ripio_get_deposit_accounts Ripio deposit accounts (CVU) ~56
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| accounts | array | yes | – |
| warnings | array | yes | – |
No examples provided.
ripio_get_deposit_address Ripio deposit address ~146
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.
| Name | Type | Req | Description |
|---|---|---|---|
| asset | string | yes | Ripio ticker, e.g. USDT, BTC or AAPLx. |
| network | string | – | The network as the sender names it: code, name or token standard, e.g. tron, "BNB Chain", TRC20, BEP-20. |
| Name | Type | Req | Description |
|---|---|---|---|
| asset | string | yes | – |
| asset_name | string | – | – |
| deposit | object | – | – |
| networks | array | yes | – |
| next_step | string | – | – |
| status | string | yes | – |
| warnings | array | yes | – |
No examples provided.
ripio_get_limits Ripio limits and rails ~76
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.
| Name | Type | Req | Description |
|---|---|---|---|
| rail | string | – | – |
| type | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| limits | array | yes | – |
| note | string | yes | – |
| rails | array | yes | – |
No examples provided.
ripio_get_portfolio Ripio portfolio ~88
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.
| Name | Type | Req | Description |
|---|---|---|---|
| include_zero | boolean | – | Include assets with a zero balance. Default false. |
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | string | yes | – |
| holdings | array | yes | – |
| totals | object | yes | – |
| valuation | object | yes | – |
| warnings | array | yes | – |
No examples provided.
ripio_get_prices Ripio prices ~95
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.
| Name | Type | Req | Description |
|---|---|---|---|
| assets | array | yes | Tickers, e.g. ["USDT", "BTC"]. |
| quote | string | – | Default "ARS". |
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | string | yes | – |
| not_found | array | yes | – |
| prices | array | yes | – |
| quote | string | yes | – |
| warnings | array | yes | – |
No examples provided.
ripio_get_transaction Ripio Wallet transaction ~71
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | – | yes | Wallet transaction id, as a number or as the string ripio_list_activity returns. |
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | yes | – |
| asset | string | yes | – |
| counterparty | string | – | – |
| date | string | yes | – |
| description | string | – | – |
| direction | string | yes | – |
| fee | string | – | – |
| fee_asset | string | – | – |
| id | string | yes | – |
| rail | string | – | – |
| raw_status | string | yes | – |
| status | string | yes | – |
| transaction_hash | string | – | – |
| type | string | yes | – |
| unreadable | array | – | – |
No examples provided.
ripio_list_activity Ripio activity ~214
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.
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | – | Only this asset, e.g. "USDT". |
| cursor | string | – | next_cursor from a previous call. |
| from | – | – | UTC date (YYYY-MM-DD) or ISO 8601 date-time. |
| rail | string | – | Wallet only. |
| source | string | – | Default "wallet". |
| to | – | – | UTC date (YYYY-MM-DD) or ISO 8601 date-time. |
| type | string | – | "trade" exists only in source "trade"; "swap" only in "wallet". |
| Name | Type | Req | Description |
|---|---|---|---|
| coverage_notes | array | yes | – |
| items | array | yes | – |
| next_cursor | string | – | – |
| source | string | yes | – |
No examples provided.
ripio_list_open_orders Ripio Trade open orders ~74
Open orders on Ripio Trade, optionally for one pair or side, with price and requested, executed and remaining amounts.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | next_cursor from a previous call. |
| pair | string | – | Ripio Trade pair, e.g. USDT_ARS. |
| side | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| next_cursor | string | – | – |
| orders | array | yes | – |
No examples provided.
ripio_verify_deposit_address Verify a Ripio deposit address ~193
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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | The address exactly as pasted. |
| asset | string | – | Ripio ticker, e.g. USDT, BTC or AAPLx. |
| memo | string | – | Memo/tag as pasted, for networks that use one (XRP, Stellar, TON). |
| network | string | – | The network as the sender names it: code, name or token standard, e.g. tron, "BNB Chain", TRC20, BEP-20. |
| Name | Type | Req | Description |
|---|---|---|---|
| address_networks | array | yes | – |
| asset | string | – | – |
| credited_via | array | – | – |
| expected_memo | string | – | – |
| near_miss | object | – | – |
| not_credited_via | array | – | – |
| status | string | yes | – |
| verdict | string | yes | – |
| warnings | array | yes | – |
No examples provided.
What is the Ripio (community, read-only) MCP server?
Ripio (community, read-only) is an MCP server listed in the public MCP registry as io.github.ruizemanuel/ripio-community-mcp. Unofficial, read-only MCP server for your Ripio account: balances, activity, prices and deposits. This page covers its npm package (ripio-community-mcp).
Is the Ripio (community, read-only) MCP server safe to use?
Ripio (community, read-only) scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 26 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Ripio (community, read-only) MCP server expose?
Ripio (community, read-only) exposes 10 tools: ripio_get_portfolio, ripio_list_activity, ripio_get_transaction, ripio_get_prices, ripio_estimate_trade, and 5 more. Their descriptions and schemas cost roughly 1,120 tokens of context every time the server is loaded.
Is the Ripio (community, read-only) MCP server still maintained?
Ripio (community, read-only) is still listed as active in the MCP registry. We last reached this channel on 26 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Ripio (community, read-only) MCP server under?
Ripio (community, read-only) declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.