mcpbeat

EmidLabs Backtest MCP Server

io.github.emidlabs/backtest-mcp
answering

EmidLabs Backtest is answering right now. Last checked 8 min ago. It exposes 3 tools.

Run crypto trading strategy backtests through EmidLabs's Backtesting API.

The linked repository no longer exists on GitHub — it was deleted or made private.

Uptime history 45 hours of history
45 hours agonow
100.0%
Uptime 24h
91 of 91 checks
3
Tools
read from the server
349 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 8 min ago.

run in your terminal
claude mcp add backtest-mcp --transport http https://mcp.backtest.emidlabs.com/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "backtest-mcp": {
      "url": "https://mcp.backtest.emidlabs.com/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.backtest-mcp]
url = "https://mcp.backtest.emidlabs.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "backtest-mcp": {
      "url": "https://mcp.backtest.emidlabs.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "backtest-mcp": {
      "url": "https://mcp.backtest.emidlabs.com/mcp"
    }
  }
}

Available tools 3

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

available
list_available_assets
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 exploration or for recovering from an "unknown asset" error, not a required step before every submit_backtest.
backtest
get_backtest_result
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. Trade-level detail is intentionally omitted; only aggregate metrics are returned.
submit
submit_backtest
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.

Endpoints

URLTransportStateLatencyChecked
https://mcp.backtest.emidlabs.com/mcp streamable-http answering 298 ms 8 min ago

EmidLabs Backtest — questions

Answers built from our own checks of this server.

What can EmidLabs Backtest do?
It exposes 3 tools, read directly from the server on our last check. Among them: get_backtest_result, list_available_assets, submit_backtest. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is EmidLabs Backtest working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 349 ms. The bar chart above shows every period we have measured.
Is EmidLabs Backtest still maintained?
The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.
How do I connect EmidLabs Backtest?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does EmidLabs Backtest need an API key?
No. EmidLabs Backtest completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 3 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is EmidLabs Backtest?
It answers our handshake in 349 ms on average, which is faster than 40% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.