MCP App Store
by KeenEthics
Manifold-BT Backtest icon

Manifold-BT Backtest MCP Server for Claude

By Manifold-BT

Overview

Manifold-BT Backtest turns a question about a trading rule into a research workflow that Claude runs in its own code environment. Step 1 installs the Manifold-BT backtesting engine from PyPI. Each following step runs there, on the bars you upload (CSV or Parquet) or on a synthetic series, and prints a few numbers. The connector checks them against a written gate (enough trades, a Sharpe ratio distinguishable from zero, a result that survives doubled costs and a one-bar delay, a parameter choice that beats what the same search finds in noise) and hands over the next step, a retry with the reason, or the verdict. Five workflows: test an idea; tune parameters by keeping the stable region instead of the single best cell; validate out of sample; size exposure when the edge is an estimate; diagnose a result that looks too good. The connector computes nothing and stores nothing: your data and strategy stay in Claude's environment. No account is needed. Code execution with network access to package managers must be enabled in Claude. A backtest measures a rule on past data; it is not a forecast and not investment advice.

How to connect

  1. Claude: Open the Manifold-BT Backtest listing in the Claude connectors directory and choose Connect. Claude listing Manifold-BT Backtest exposes 5 tools here.

Tools

check_step

Claude
Applies a research step's gate to the result its code printed, and returns pass, fail or warn with the reasons, then what follows: the next step with its code, a retry of this step, or the verdict step when a failed gate settles the question. result is the JSON printed after RESULT (or, for the steps without code, the fields the step lists under send_back). data_file is the path given to start_research, carried into the data step's code. Pure arithmetic on what is sent: nothing is stored.

explain_error

Claude
Explain an error returned by the manifoldbt engine: what it means, what caused it, and how to fix it. Takes the message verbatim. The engine's messages name the rule that was broken rather than the mistake that broke it; this returns the mistake.

get_capabilities

Claude
Returns the manifoldbt version documented, the three licence tiers (Community, Pro, Researcher) and what each unlocks, and how each limit refuses: the Community budget of 256 sweep or batch combinations per Python process, the 1000-path Monte Carlo cap, the features refused outright on Community (run_stability, walk-forward, cross-exchange), and the GPU and tick layer reserved to Researcher, with the exception each raises.

search_docs

Claude
Search the manifoldbt documentation: DSL rules and pitfalls, indicator and API signatures, config fields, execution semantics (which price a stop or target fills at, which fee each fill pays, what a reversal counts as, which ddof an indicator uses), how to read result metrics honestly, and worked examples. Ask in natural language ('how do I reference another symbol', 'what happens when a bar gaps through my stop', 'is this Sharpe meaningful') or by name ('symbol_ref', 'warmup_bars'). Pass a result's exact title to read that chunk again. A chunk already sent in this session is not sent again.

start_research

Claude
Starts a backtesting research workflow run with the manifoldbt engine in the client's code environment. Returns the workflow's outline (each step and the gate its result must pass) and step 1 with its code: installing manifoldbt, pinned to the documented version. Each step's code ends by printing a line RESULT {json}; check_step takes that JSON and returns the next step. Workflows: test_idea, tune_parameters (surface, stable region, pooling, correction for the search), validate_out_of_sample, size_exposure, diagnose_result. workflow selects one by id, otherwise goal picks the closest. data_file is the path of the user's uploaded bars (CSV or Parquet); empty uses a synthetic series.

Similar Apps

Listed on MCP App Store

Listed on MCP App Store

Add this badge to your site or README. It links to this page.

HTML

<a href="https://mcp-app-store.keenethics-labs.com/app/manifoldbt-backtest"><img src="https://mcp-app-store.keenethics-labs.com/badges/listed-on-mcp-app-store.svg" alt="Listed on MCP App Store" width="220" height="44"></a>

Markdown

[![Listed on MCP App Store](https://mcp-app-store.keenethics-labs.com/badges/listed-on-mcp-app-store.svg)](https://mcp-app-store.keenethics-labs.com/app/manifoldbt-backtest)