← emidlabs.com

INDIVIDUAL MCP TOOL

submit_backtest

Submits a strategy for backtesting against historical OHLCV data.

emidlabs.comnone authenticationAvailability not checked

LIVE ENDPOINT

https://mcp.backtest.emidlabs.com/mcp

No auth detected

Connect to this endpoint to inspect the live schema for submit_backtest and invoke it with your own arguments.

Indexed input schema

{}

Risk classification

Inferred read-only · medium confidence · heuristic, not a guarantee.

  • No write-capable action terms were found; this is not proof that invocation has no side effects.

Parent server

emidlabs.com

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.emidlabs-backtest-mcp]
url = "https://mcp.backtest.emidlabs.com/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "emidlabs-backtest-mcp": {
      "type": "http",
      "url": "https://mcp.backtest.emidlabs.com/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: emidlabs-backtest-mcp
Remote MCP URL: https://mcp.backtest.emidlabs.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "emidlabs-backtest-mcp": {
      "url": "https://mcp.backtest.emidlabs.com/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "emidlabs-backtest-mcp": {
      "type": "http",
      "url": "https://mcp.backtest.emidlabs.com/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "emidlabs-backtest-mcp",
  "transport": "streamable-http",
  "url": "https://mcp.backtest.emidlabs.com/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

Related tools

  • list_available_assets — Lists every asset pair with real historical data, each with its supported timeframes and the date range actually available.
  • submit_backtest_batch — 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.
  • get_backtest_batch_results — Fetches every asset's outcome from a submit_backtest_batch call, paginated.
  • get_backtest_trades — Fetches the closed-trade list for a completed backtest, paginated and sortable — the trade-by-trade detail get_backtest_result deliberately omits.
  • get_backtest_result — Fetches a submitted backtest by id.