Skip to main content
Glama
CaioAllgayer

TradeLab-MCP

by CaioAllgayer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to TradeLab-MCP

No user-submitted related servers found.

    Related Servers

    • MT5 MCP Server

      Boschi404
      F
      license
      Not graded
      quality
      A
      maintenance
      A 34-tool MCP server that bridges LLMs to MetaTrader 5, enabling EA development, backtesting, optimization, advanced analytics, live trading, and portfolio management.
      1
      -
    • backtest360-mcp by Backtest360

      backtest360-mcpofficial

      Backtest360
      A
      license
      A
      quality
      D
      maintenance
      MCP server that exposes the Backtest360 backtesting engine API as tools, enabling AI agents to conversationally discover indicators, build and validate strategies, run backtests, and read results.
      14
      60 PyPI
      MIT

    • MT5-MCP

      Roan2802
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables LLMs to compile Expert Advisors, run MetaTrader 5 strategy backtests with arbitrary settings, and receive structured testing results as MCP tools.
      -

    • FinClaw

      IlyasFardaouix
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that provides AI agents with financial tools including real-time quotes, backtesting, technical analysis, and multi-exchange data via a simple CLI interface.
      1
      MIT

    • APEX Research MCP Server

      junaidshahid-dev
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables quantitative trading research by providing tools to backtest strategies, list market datasets, review forward-test logs, and search previously rejected hypotheses, all through an MCP interface.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.3/5.0

    Scored across 18 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: terminal management, compilation, single/batch/walk-forward backtests, result retrieval/comparison, and EA registry operations. The run-related tools are differentiated by scope and description, so an agent is unlikely to confuse them.

    Naming Consistency4/5

    Most tools follow a clear verb_noun pattern such as list_terminals, run_backtest, get_trades, and refresh_ea_registry. A few exceptions like health, compile, ea_capabilities, and walk_forward are readable but break the otherwise consistent convention.

    Tool Count4/5

    At 18 tools, this is slightly above the typical 3-15 tool sweet spot, but the count is justified by the distinct environment, backtest, results, and EA-registry concerns. Each tool has a clear role and none feel redundant.

    Completeness3/5

    Core workflows are well covered: environment health, compilation, backtests, walk-forward, smoke tests, and result inspection/comparison. However, there is no run listing/deletion tool and no direct EA generation/modification tool, which leaves notable gaps in lifecycle management.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources