Skip to main content
Glama
roman-zaglauer

OctoBot MCP Server

Related Servers

Alternatives to OctoBot MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to discover trading domains, inspect bots, backtest and submit crypto trading strategies for validation and live deployment, and monitor tournament and leaderboard status via MCP tools.
      9
      MIT
    • 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
    • F
      license
      B
      quality
      D
      maintenance
      Connects MCP-compatible AI agents to GT Protocol trading accounts, enabling natural language control of automated trading bots, strategy backtesting, deal execution, and balance monitoring on Binance and Hyperliquid exchanges.
      1
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server for cryptocurrency trading via Freqtrade, enabling trade management, balance checks, strategy configuration, backtesting, and bot lifecycle control from any MCP-compatible AI agent.
      MIT
    • A
      license
      Not graded
      quality
      C
      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

    TDQS

    A4.1/5.0

    Scored across 47 tools

    Disambiguation4/5

    Most tools pair a single action with a distinct OctoBot resource, and the profile, trading, job, and config families are separated cleanly. A few near-miss names such as get_currency_list vs get_all_currencies, and list_tentacles vs list_evaluators, create enough ambiguity that an agent has to rely on the descriptions.

    Naming Consistency4/5

    The set is uniformly snake_case and mostly follows a verb_noun pattern (get_orders, create_profile, clear_trades_history, start_backtest). It is not perfectly regular because collection-returning tools mix get_ and list_ prefixes, and a few names use phrasal forms like check_accounts_compatible or convert_profile_to_live.

    Tool Count3/5

    47 tools is well above the typical well-scoped MCP surface and will impose real selection overhead, especially with two stub tools that do not perform their apparent function. The breadth is partly justified by OctoBot's many domains, but the set would be tighter if the four clear_*_history tools and related listing tools were consolidated.

    Completeness3/5

    Profile CRUD, job lifecycle, data-file management, and the evaluator update/listing loop are complete. However, the trading surface lacks any order-creation or live-trading toggle, list_tentacles and get_logs are explicit stubs, and tentacle discovery outside evaluators is a dead end, so there are notable gaps.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues