Skip to content

EmidLabs Backtest MCP server

io.github.emidlabs/backtest-mcpemidlabsstreamable-httpv0.1.0Scanned

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

9 tools: 3 change things and 6 only read.

Tools: 0 delete, 0 irreversible, 3 write, 6 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

The remote endpoint did not answer the last look. Remote posture

Anlyon alternative

3 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the EmidLabs Backtest MCP server can do

The EmidLabs Backtest MCP server is published by the GitHub account emidlabs. It has 9 tools. It can create or change data (3 tools: submit_confirmation_source, submit_backtest_batch and submit_backtest), but cannot delete data. 6 tools only read.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Last scanned Nov 5, 2026, version 0.1.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

9 tools

Changes things 3Claude Code: ask
  • submit_backtestSubmits a strategy for backtesting against historical OHLCV data.No findings

    Why it is in this group

    • The name "submit_backtest" says "submit": a word for a change.
    Description, as the server wrote it
    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. Optionally accepts confirmationSources to only count a candidate Entry/Exit as a real trade once corroborated by a submit_confirmation_source result (multi-timeframe or cross-asset confirmation) — see the confirmationSources argument and submit_confirmation_source's own description.

    Annotations the server declares

    • title: Submit Backtest
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
    • readOnlyHint: false
  • submit_backtest_batchSubmits 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.No findings

    Why it is in this group

    • The name "submit_backtest_batch" says "submit": a word for a change.
    Description, as the server wrote it
    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 the per-asset id/status assigned right away. Best-effort: one bad asset pair (unknown, or its date range outside coverage) shows up with an error in that item only — every other asset in the batch is unaffected. Optionally accepts confirmationSources, applied identically to every asset in the batch — see submit_backtest's own confirmationSources argument for the full semantics.

    Annotations the server declares

    • title: Submit Backtest Batch
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
    • readOnlyHint: false
  • submit_confirmation_sourceRuns a strategy against historical data purely to produce a signal timeline used to confirm OTHER backtests — not a backtest itself.No findings

    Why it is in this group

    • The name "submit_confirmation_source" says "submit": a word for a change.
    Description, as the server wrote it
    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, because this strategy is never meant to be traded on its own. Returns immediately with an id and status — call get_confirmation_source to check completion, then pass that id as a confirmationSources sourceId in submit_backtest (e.g. only count an XRP entry once a BTC-neutral confirmation source agrees). Costs the same capacity as a regular backtest of the same size — the compute is identical, it just skips trade simulation.

    Annotations the server declares

    • title: Submit Confirmation Source
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
    • readOnlyHint: false
Only reads 6Show 6 read-only tools
  • get_backtest_batch_resultsFetches every asset's outcome from a submit_backtest_batch call, paginated.No findings

    Why it is in this group

    • The name "get_backtest_batch_results" says "get": a word for reading.
    Description, as the server wrote it
    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 metrics and recency fields (recentTradeCount/recentAvgPnlR/recentOutcomes) get_backtest_result returns for a single backtest, plus assetPair/status/error, so the single-result and batch-result shapes never drift apart. totalCount/completedCount/failedCount/pendingCount come back on every page, not just the last, so you can tell the batch is done from a single pageSize=1 call.

    Annotations the server declares

    • title: Get Backtest Batch Results
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • get_backtest_resultFetches a submitted backtest by id.No findings

    Why it is in this group

    • The name "get_backtest_result" says "get": a word for reading.
    Description, as the server wrote it
    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 (paginated, sortable). Fetching many results from the same submit_backtest_batch call? Use get_backtest_batch_results instead.

    Annotations the server declares

    • title: Get Backtest Result
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • get_backtest_tradesFetches the closed-trade list for a completed backtest, paginated and sortable — the trade-by-trade detail get_backtest_result deliberately omits.No findings

    Why it is in this group

    • The name "get_backtest_trades" says "get": a word for reading.
    Description, as the server wrote it
    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="exitTime", sortDirection="desc", pageSize=5 for the most recently closed trades.

    Annotations the server declares

    • title: Get Backtest Trades
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • get_confirmation_sourceFetches a submitted confirmation source by id.No findings

    Why it is in this group

    • The name "get_confirmation_source" says "get": a word for reading.
    Description, as the server wrote it
    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 as a confirmationSources sourceId in submit_backtest; its raw signal timeline is available separately via get_confirmation_source_signals.

    Annotations the server declares

    • title: Get Confirmation Source
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • get_confirmation_source_signalsFetches a completed confirmation source's raw signal timeline, paginated — the actual data a backtest's confirmationSources requirement is checked against.No findings

    Why it is in this group

    • The name "get_confirmation_source_signals" says "get": a word for reading.
    Description, as the server wrote it
    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), which is why this is paginated from the start. Debugging/inspection only — you do NOT need this tool to make confirmationSources work, and should not fetch these rows to reconstruct the gating yourself. To actually gate a backtest by this source, pass its id directly as sourceId in submit_backtest's own confirmationSources array; the backend applies the backward-only state check against this exact timeline automatically, including the higher-timeframe-to-lower-timeframe alignment. Reimplementing that alignment by hand from this raw data is unnecessary and easy to get wrong (e.g. failing to correctly persist a higher-timeframe state across every lower-timeframe candle until the next higher-timeframe close). Use this tool only to sanity-check a source's signal density or diagnose an unexpectedly low ConfirmedSignalsCount after the fact.

    Annotations the server declares

    • title: Get Confirmation Source Signals
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • list_available_assetsLists every asset pair with real historical data, each with its supported timeframes and the date range actually available.No findings

    Why it is in this group

    • The name "list_available_assets" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List Available Assets
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

The remote endpoint did not answer the last look

Looked at Nov 20, 2026, 19:04 UTC, unchanged since Nov 13, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
no
HTTP status of an anonymous initialize
not observed
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

The probe stopped: The operation was aborted due to timeout

Posture changes

  1. Nov 13, 2026
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 3 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://mcp.backtest.emidlabs.com/.well-known/oauth-protected-resource to none
    • Authorization servers: https://console.api.emidlabs.com to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 6 more).View diff
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 3 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://mcp.backtest.emidlabs.com/.well-known/oauth-protected-resource to none
    • Authorization servers: https://console.api.emidlabs.com to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed

Install

Pinned to version 0.1.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http backtest https://mcp.backtest.emidlabs.com/mcp
claude mcp add --transport http backtest https://mcp.backtest.emidlabs.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__backtest__list_available_assets",
      "mcp__backtest__get_backtest_batch_results",
      "mcp__backtest__get_backtest_trades",
      "mcp__backtest__get_backtest_result",
      "mcp__backtest__get_confirmation_source",
      "mcp__backtest__get_confirmation_source_signals"
    ],
    "ask": [
      "mcp__backtest__submit_confirmation_source",
      "mcp__backtest__submit_backtest_batch",
      "mcp__backtest__submit_backtest"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as backtest. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.emidlabs/backtest-mcp/verify?hash=38d14ae086a5380f708229f28e81210047ef67681371f00d4a9e1bff5224fc91" | jq -e '.changed == false'

Pinned hash 38d14ae086a5, from Nov 5, 2026, 18:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.emidlabs/backtest-mcp/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.emidlabs/backtest-mcp
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.emidlabs/backtest-mcp.svg)](https://radar.anlyon.com/servers/io.github.emidlabs/backtest-mcp)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:33 UTC.

EmidLabs Backtest MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the EmidLabs Backtest MCP server safe?

No scan can promise that. What its definitions show: 9 tools, 3 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the EmidLabs Backtest MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the EmidLabs Backtest MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the EmidLabs Backtest MCP server have?

9 tools: 3 write, 6 read. submit_confirmation_source, submit_backtest_batch, submit_backtest, list_available_assets, get_backtest_batch_results, get_backtest_trades, get_backtest_result, get_confirmation_source and 1 more.

Does the EmidLabs Backtest MCP server need sign-in or OAuth?

Its remote endpoint did not answer the last anonymous look.

Does the EmidLabs Backtest MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the EmidLabs Backtest MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 5, 2026.