Backtest360

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

• Connection: Computer or cloud
• Transport: stdio, Streamable HTTP
• Category: Other
• You need to fill in: BACKTEST360_API_KEY, X-API-Key

Install

Pick the AI app you use, then copy the settings.

You need

• Runs in the cloudNothing to install; it connects over the internet
• PyPIPython’s uv installed (for the uvx command)

Which app do you use?

{
  "mcpServers": {
    "backtest360": {
      "command": "uvx",
      "args": [
        "backtest360-mcp"
      ],
      "env": {
        "BACKTEST360_API_KEY": "your-value"
      }
    }
  }
}

claude mcp add --transport http backtest360 https://mcp.backtest360.com/mcp --header 'X-API-Key: your-value'

claude mcp add backtest360 --env BACKTEST360_API_KEY=your-value -- uvx backtest360-mcp

{
  "mcpServers": {
    "backtest360": {
      "url": "https://mcp.backtest360.com/mcp",
      "headers": {
        "X-API-Key": "your-value"
      }
    }
  }
}

{
  "mcpServers": {
    "backtest360": {
      "command": "uvx",
      "args": [
        "backtest360-mcp"
      ],
      "env": {
        "BACKTEST360_API_KEY": "your-value"
      }
    }
  }
}

{
  "servers": {
    "backtest360": {
      "type": "http",
      "url": "https://mcp.backtest360.com/mcp",
      "headers": {
        "X-API-Key": "your-value"
      }
    }
  }
}

{
  "servers": {
    "backtest360": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "backtest360-mcp"
      ],
      "env": {
        "BACKTEST360_API_KEY": "your-value"
      }
    }
  }
}

Your choice stays on this device in a cookie; no account needed.

Values you fill in

• BACKTEST360_API_KEY secret required env
  Backtest360 engine API key, sent to the engine as X-API-Key. Get a free key at https://backtest360.com/api-access.
• X-API-Key secret required HTTP header
  Backtest360 engine API key, sent to the hosted MCP server as X-API-Key. Get a free key at https://backtest360.com/api-access.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Tool names and descriptions exactly as the server reported them on Nov 10, 2026. The maker wrote them, not us; we show them as plain text.

• get_me

  The configured API key's permissions, limits, and current usage. Cheap. Call early in a session — before planning work — to learn what this key can do instead of discovering limits through failed calls. Returns: ``scopes``: the permission scopes the key carries. ``limits``: reque

• engine_info

  Engine version, API contract number, and health. Free (not quota-counted). Call once at the start of a session to confirm the engine is reachable and which contract it serves.

• get_catalog

  Fetch one engine reference catalog. Catalogs (cheap, cacheable per session): - 'operators' — comparison operators for condition expressions - 'execution-modes' — entry/exit anchors and fill algorithms, with the validity matrix by market type - 'stop-types' — stop-loss types, re-e

• list_indicators

  List indicators, or fetch one indicator's full schema. Cheap, cacheable per session. With no arguments: a compact catalog — ``{"indicators": [...], "count": N}`` — where each entry carries id, name, category, kind, and value_dtype (no description, to keep the discovery scan small

• list_templates

  List predesigned strategy templates, or fetch one in full. Cheap, cacheable per session. The engine returns the templates available to the calling key. With no arguments: a compact catalog — ``{"templates": [...], "count": N}`` — where each entry carries id, origin, name, and des

• get_strategy_schema

  JSON Schema for the strategy document (condition_tree + indicators). Fetch this before composing a strategy by hand; the validate_strategy tool checks against the same rules.

• validate_strategy

  Validate a strategy document without running a backtest. A cheap quota separate from backtest runs, so validate freely and ALWAYS before run_backtest. Args: strategy: The strategy document — name, indicators[], and condition_tree (see get_strategy_schema for the exact shape). inj

• run_backtest

  Run a historical backtest against the engine. Quota-counted and compute-bound. Validate the strategy first (validate_strategy is far cheaper). On a 504 compute timeout, do NOT retry the same request — reduce the date range, use a coarser frequency, or simplify the strategy. On 42

• get_latest_signal

  Evaluate the strategy on the most recent bar only — no P&L, no stats. Returns the latest signal (-1/0/1), which condition slots fired, and the bar timestamp. Use for "what would this strategy do right now" questions; use run_backtest for performance.

• compare_backtests

  Run several strategies on the same data and compare side by side. One quota-counted call, but compute scales with the number of strategies. If the wall-clock compute budget is exceeded, the call fails with a tool error (504) instead of returning partial results — narrow the reque

• export_backtest

  Export a multi-strategy comparison as an Excel workbook. Quota-counted; needs a key whose plan includes full-metrics export (a 403 means the configured key's plan does not — do not retry). Returns the workbook base64-encoded — decode and write it to a ``.xlsx`` file. Args: data_s

• compute_stats

  Compute the engine's performance metrics from a returns series. Use when the returns came from somewhere other than run_backtest (an external system, a portfolio) — backtest results already include these statistics. Args: returns: Per-bar log returns as {"dates": [...], "values":

• search_tickers

  Search available assets by ticker or name (relevance-ranked). Use to resolve a user's asset mention ("bitcoin", "S&P") to the exact ticker before requesting a server-side data fetch. asset_class filters to 'stocks', 'crypto', 'forex', or 'indices'.

• list_tickers

  List available tickers, optionally filtered by asset class. The full universe is very large, so the MCP server caps the returned list and marks it ``truncated_by_mcp`` — pass asset_class to narrow it, or use search_tickers to resolve a specific asset by name.

• get_data_range

  Available date range and estimated bar count for a symbol/frequency. Available on paid plans. Call before a server-side fetch so the requested start/end stay inside what the provider can deliver and the bar count stays inside the key's per-run limit.

• get_ticker_info

  Identity and data coverage for one symbol, in a single call. Metadata only — no market data, so no paid plan is needed. Returns the asset's identity (name, asset class, exchange, currency, and whether it is still active) together with a coverage summary for the given frequency: t

• get_quote

  Latest available price for a symbol. Requires a paid plan (managed market data). Returns the most recent *available* bar for the given frequency — the end-of-day close for daily, the last completed bar otherwise — as open/high/low/close/volume plus an ``as_of`` timestamp for that

• get_price_history

  OHLCV price history for a symbol over a date range. Requires a paid plan (managed market data). ``start`` is required (``YYYY-MM-DD``); ``end`` defaults to today. Returns a summary (symbol, resolved date range, total bar count, price range, gap flags), market-hours detection, and

• list_macro_series

  List the available macroeconomic series (the catalog). Free — no special plan. Returns the set of macro series you can fetch with get_macro_series, each with its stable ``id`` (the value get_macro_series takes), title, category, native reporting frequency, and units, plus the lis

• get_macro_series

  Observations for one macroeconomic series over an optional date range. Free — no special plan. ``series`` is an ``id`` from list_macro_series (e.g. treasury_10y, cpi, unemployment_rate); arbitrary external ids are not accepted. ``start``/``end`` are ``YYYY-MM-DD``, inclusive, bot

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 10, 2026

• ✓ Pass

  Maker matches the repo

  The registry name was verified against the domain backtest360.com (the registry checks domain ownership)

• … Not checked yet

  Still maintained

  We have not read this repo from GitHub yet

• … Not checked yet

  Has a licence

  We have not read this repo from GitHub yet

• ✓ Pass

  Endpoint responds

  Responded in 145 ms (HTTP 200)

• – Not applicable

  Sign-in with OAuth

  No sign-in needed

• ✓ Pass

  No hidden instructions in tool descriptions

  Read 20 tool descriptions and found no hidden instructions to the AI

Compared with others in Otheri

• More stars than 0% of the other 18994 servers in this category
• Published to the registry more recently than 17% of the other 18994 servers in this category
• Basic checks equal to or better than 100% of the other 18994 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

README from the maker

pip install backtest360-mcp        # or, from a clone: pip install -e .

{

{

pip install -e ".[dev]"