Skip to main content
Glama
Backtest360

backtest360-mcp

Official
by Backtest360
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to backtest360-mcp

No user-submitted related servers found.

    Related Servers

    • diepi-mcp

      elonmaskhair-prog
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for natural-language daily stock/ETF strategy backtesting. It provides constrained tools for strategy specification, data validation, queue-based backtests, and verifiable result artifacts.
      1
      Apache 2.0

    • TradeMCP

      Aaditya2502
      A
      license
      A
      quality
      D
      maintenance
      An MCP server that exposes trading analytics — technical indicators, portfolio state, risk metrics, and backtest results — as tools an LLM agent can call.
      5
      MIT

    • Jesse MCP Server

      bkuri
      A
      license
      C
      quality
      C
      maintenance
      An MCP server that exposes the Jesse algorithmic trading framework's capabilities to LLM agents for backtesting, optimization, and risk analysis. It provides 32 specialized tools for managing trading strategies and performing comprehensive market simulations via the Jesse REST API.
      69
      10 PyPI
      22
      MIT

    • 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
    • cpzai-mcp-server by CPZ-Lab

      cpzai-mcp-serverofficial

      CPZ-Lab
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for CPZAI platform, enabling AI agents to manage trading strategies, run backtests, route orders across brokers, and access portfolios, risk analytics, and market data through natural language.
      1
      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

    A4.5/5.0

    Scored across 14 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: validation, backtest execution, comparison, statistics, catalog browsing, ticker search, etc. Overlaps are minimal and clearly differentiated (e.g., get_latest_signal returns current signal only, run_backtest returns full performance).

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case (e.g., validate_strategy, run_backtest, list_indicators). No mixing of conventions like camelCase or inconsistent verb styles.

    Tool Count5/5

    14 tools is well within the 3-15 ideal range. Each tool serves a necessary function for the backtesting domain—validation, execution, analysis, discovery—without bloat or missing essentials.

    Completeness4/5

    Covers the core backtesting workflow: strategy creation (schema, validation), execution (run, compare, signal), data discovery (tickers, range), and analysis (stats). Minor gaps: no tool for editing saved strategies or managing user settings, but these are peripheral to the server's main purpose.

    Maintenance

    ActivityStale
    ResponsivenessUnresponsive

    Resources