ripio-community-mcp
Related Servers
Alternatives to ripio-community-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceA read-only MCP server for Trading 212 accounts, enabling AI assistants to query balances, positions, orders, dividends, pies, and instruments without trading capabilities.121MIT

@luxalgo/broker-mcpofficial
AlicenseAqualityBmaintenanceA local MCP server that gives AI agents read-only access to real brokerage accounts across 16 brokers and exchanges, while keeping API keys on the user's machine. It enables portfolio overviews, positions, trade history, and performance statistics through natural-language queries.61MIT- AlicenseNot gradedqualityBmaintenanceA read-only MCP server that securely connects Swedish/Nordic bank accounts to AI assistants, keeping all financial data local and encrypted.19 npmMIT

milele-prime-mcpofficial
FlicenseNot gradedqualityCmaintenanceRead-only MCP server that lets a verified client connect their own AI to their trading account to read account data without order execution.-- AlicenseNot gradedqualityCmaintenanceA read-only MCP server for Hyperliquid that provides public market data (prices, order books, funding) and any wallet's positions, orders, and fills via MCP tools, without requiring a private key.MIT
- AlicenseNot gradedqualityAmaintenanceRead-only MCP server that connects LLMs to personal investment accounts (Toss Securities, KIS), market data, SEC filings, and Binance futures for context-aware investment responses.1MIT
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.