Skip to main content
Glama
ripio-community-mcp

ripio-community-mcp

by ruizemanuel

Related Servers

Alternatives to ripio-community-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      A read-only MCP server for Trading 212 accounts, enabling AI assistants to query balances, positions, orders, dividends, pies, and instruments without trading capabilities.
      12
      1
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      A 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.
      6
      1
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A read-only MCP server that securely connects Swedish/Nordic bank accounts to AI assistants, keeping all financial data local and encrypted.
      22 npm
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      A read-only Model Context Protocol server that lets AI agents query brokerage account holdings, balances, real-time quotes, price history, options chains, orders, and transactions, with account masking and LLM-friendly output.
      14
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      A read-only MCP server that lets individual investors ask AI chat clients about their own brokerage and crypto futures accounts alongside public market data, SEC filings, and ticker research, without any order or transfer capabilities.
      28
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Read-only MCP server that lets a verified client connect their own AI to their trading account to read account data without order execution.
      -

    TDQS

    A4.4/5.0

    Scored across 10 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivitySlowing
    ResponsivenessNo recent community issues