Skip to main content
Glama
Rufus011

CMP-server Pocket Option 2026

by Rufus011

Related Servers

Alternatives to CMP-server Pocket Option 2026

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to interact with Interactive Brokers through 48 tools for market data, orders, account management, and more, via the MCP protocol.
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables LLMs to trade on MetaTrader 5 via REST API or MCP tools, supporting market/pending orders, position management, and account info retrieval.
      -
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables agents to access live crypto market data and execute risk-controlled paper trades through standardized MCP tool calls.
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants in MCP clients to query real-time market data, inspect portfolio and Web3 wallet balances across brokers, place protected equity/ETF, crypto, forex, options, DeFi swap, and prediction market orders, and run backtests.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Connects AI assistants to 16 crypto exchanges and MetaTrader 5 over a single MCP endpoint, enabling trading and account management with server-side risk controls, paper trading by default, and auditable signed receipts.
      3
      CC BY-4.0
    • A
      license
      B
      quality
      D
      maintenance
      Enables AI agents to trade crypto with paper money, access market data, view leaderboards, and manage trading bots via an MCP-compatible interface.
      16
      MIT

    TDQS

    A3.7/5.0

    Scored across 24 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: market data (get_candles, get_price), trading (place_trade, check_result), account/trade history (get_balance, open_positions, trade_history), memory (strategies vs skills), and communication (opinions vs messages). No two tools overlap enough to cause misselection.

    Naming Consistency3/5

    Naming is readable but mixes patterns: get_* and list_* for retrieval, save_*/delete_* for memory, plus noun-only names like performance, trade_history, and open_positions. The inconsistent use of get vs list and the non-verb names prevent a higher score, though the verbs are descriptive.

    Tool Count3/5

    24 tools falls in the 16-25 'heavy' range, but the scope includes three distinct domains (trading, persistent memory, agent communication), so each cluster earns its place. It is slightly over a typical well-scoped server but not excessive.

    Completeness4/5

    The trading lifecycle is well covered: market data, balance, trade placement, result checking, open positions, and history. Memory and communication are also complete with CRUD for strategies/skills and send/read for opinions/messages. Minor gaps exist (e.g., no individual opinion deletion, no market news), but core workflows have no dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues