MCP server
EmidLabs Backtest Official
io.github.emidlabs/backtest-mcp
Checked 25 Oct 2026, 20:29 UTC · Connected to it and listed its tools
Run crypto trading strategy backtests through EmidLabs's Backtesting API.
Working at last checkOfficial: emidlabs.com's GitHub account (emidlabs)About 9,613 tokens per request once connected9 tools
https://mcp.backtest.emidlabs.com/mcp
At a glance
- Type
- MCP server
- Publisher
- emidlabs.com (verified by the MCP Registry)
- Status
- Working at last check
- Tools
- 9
- Token cost
- About 9,613 tokens per request
- Sets up in
- Claude Code, Claude Desktop, Codex, Gemini CLI, Cursor, VS Code, Antigravity, ChatGPT, OpenAI API, Grok
- Last checked
- 25 Oct 2026, 20:29 UTC
Connect it to your agent
Opens the app, which shows the server and asks you to confirm. For other apps, copy the setup below.
Claude Code
claude mcp add --transport http backtest-mcp https://mcp.backtest.emidlabs.com/mcp
Claude Desktop
Settings → Connectors → Add custom connector, and paste the URL.
Codex (config.toml)
[mcp_servers.backtest-mcp] url = "https://mcp.backtest.emidlabs.com/mcp"
Gemini CLI
{"mcpServers":{"backtest-mcp":{"httpUrl":"https://mcp.backtest.emidlabs.com/mcp"}}}
Cursor
{"mcpServers":{"backtest-mcp":{"url":"https://mcp.backtest.emidlabs.com/mcp"}}}
VS Code
{"servers":{"backtest-mcp":{"type":"http","url":"https://mcp.backtest.emidlabs.com/mcp"}}}
Antigravity
agy mcp add backtest-mcp https://mcp.backtest.emidlabs.com/mcp
ChatGPT
Settings → Apps & Connectors → Advanced settings: turn on Developer mode, then Create a connector and paste the URL. Which plans can do this varies.
OpenAI API (Responses tools)
{"type":"mcp","server_label":"backtest-mcp","server_url":"https://mcp.backtest.emidlabs.com/mcp","require_approval":"always"}
Grok (xAI API tools)
{"type":"mcp","server_label":"backtest-mcp","server_url":"https://mcp.backtest.emidlabs.com/mcp"}
Tools
get_backtest_batch_results~498 tokens
Fetches every asset's outcome from a submit_backtest_batch call, paginated. By default (waitForCompletion: true) polls internally until every item in the batch is done — a cheap check, not one that pages through everything — so one call returns the finished page. Each item has the same aggregate metget_backtest_result~334 tokens
Fetches a submitted backtest by id. By default (waitForCompletion: true) polls internally until it finishes, so one call returns one final answer — no need to poll from the caller's side. Only aggregate metrics are returned here, no trade-by-trade detail — call get_backtest_trades for that (paginateget_backtest_trades~376 tokens
Fetches the closed-trade list for a completed backtest, paginated and sortable — the trade-by-trade detail get_backtest_result deliberately omits. Only closed trades ever appear; a position still open when the backtest's date range ends isn't represented here or anywhere else. Example: sortBy="exitTget_confirmation_source~347 tokens
Fetches a submitted confirmation source by id. By default (waitForCompletion: true) polls internally until it finishes, so one call returns one final answer. No trade-outcome fields here at all (no PnlR/WinRate/...) — a confirmation source never opens a position. Once Completed, its id can be used aget_confirmation_source_signals~526 tokens
Fetches a completed confirmation source's raw signal timeline, paginated — the actual data a backtest's confirmationSources requirement is checked against. Can easily run into the thousands for a frequent condition over a long range (every candle-condition match is a row, not just closed trades), whlist_available_assets~240 tokens
Lists every asset pair with real historical data, each with its supported timeframes and the date range actually available. Optional to call — submit_backtest already returns a clear error (with the real available range) when an asset or date range doesn't have data, so this is for up-front exploratsubmit_backtest~2725 tokens
Submits a strategy for backtesting against historical OHLCV data. Returns immediately with an id and status — call get_backtest_result to fetch the outcome once it finishes. Testing the same strategy against many assets? Use submit_backtest_batch instead — one call per asset here adds up fast. Optiosubmit_backtest_batch~2403 tokens
Submits ONE strategy against MANY asset pairs in a single call — the same backtest you'd get from calling submit_backtest once per asset, without needing dozens of round trips. Returns immediately with a batchId (pass it to get_backtest_batch_results to fetch every asset's outcome, paginated) plus tsubmit_confirmation_source~2164 tokens
Runs a strategy against historical data purely to produce a signal timeline used to confirm OTHER backtests — not a backtest itself. Walks the same candles and evaluates the same DSL as submit_backtest, but never simulates a position: no trade, no PnL, no WinRate/drawdown, none of that applies here,
Browse
Related MCP servers
- dMoERA Creator
Build, backtest, and deploy crypto trading strategies via MCP with 7-stage validation. - Agent Einstein — Crypto & Market Intelligence
AI price forecasts, whale flows, market sentiment and prediction signals. 18 tools free, no account. - TradeAssi
Crypto tools for AI agents: live market data, exchange-wide screener, backtests and paper trading. - MangroveAI
Backtest and paper-trade crypto strategies. Free API key or pay per call in USDC (x402). - BotSpot: AI Trading, Backtests and Bots
AI agents backtest, paper trade and live trade via your broker. Free to connect; OAuth. - Sentinel Aleph
Crypto signals, public ledger, BTC chart read, news, your strategies and backtests. No trading. - PRUVIQ strategy verdicts (read-only)
Read-only crypto strategy backtest & verification verdicts. No trading tools; every result is cited. - Autotrade — Autonomous Trading Agents
Deploy autonomous LLM trading agents and drive them over MCP.
Badge for your README
[](https://aptlynx.net/servers/io.github.emidlabs/backtest-mcp)
Listing text is written by the maker; AptLynx lists tools and does not vouch for them. Find another tool · Browse by topic · For agents