Is the Emidlabs Backtest MCP server down?

mcp-registry/io.github.emidlabs/backtest-mcp · v0.1.0

As of 2026-10-20 03:00 UTC, the Emidlabs Backtest MCP server is up with a Glimind reliability score of 85/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 39 outages in 90 days, with a median recovery of 3 minutes.

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

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

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

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: A (94/100)

What to fix (2)

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.emidlabs/backtest-mcp"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.emidlabs/backtest-mcp"}) over MCP.

Passed

• Every tool has a well-formed, typed input schema.
• Every tool and parameter is described.
• Every tool declares whether it is read-only or destructive.
• No tool-poisoning patterns (hidden characters, instruction overrides, concealment, secret access, tool shadowing).
• Tool names are unique and portable across clients.
• Speaks MCP 2025-06-18.
• 99.87% uptime over 30 days.
• No breaking contract changes in 30 days.

Largest tool definitions

• submit_backtest ~2,627 tokens
• submit_backtest_batch ~2,286 tokens
• submit_confirmation_source ~2,041 tokens
• get_backtest_batch_results ~435 tokens
• get_backtest_trades ~365 tokens

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.emidlabs%2Fbacktest-mcp.svg)](https://glimind.com/server/mcp-registry%2Fio.github.emidlabs%2Fbacktest-mcp?ref=badge)

<a href="https://glimind.com/server/mcp-registry%2Fio.github.emidlabs%2Fbacktest-mcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.emidlabs%2Fbacktest-mcp.svg" alt="MCP agent-readiness"></a>

.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.emidlabs%2Fbacktest-mcp.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.emidlabs%2Fbacktest-mcp?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:dec46df02d51dd86…, first seen 2026-10-17, included at leaf 5512 of 30,347. Version history · verify what your client received.

Tools (9)

• get_backtest_batch_results
• get_backtest_result
• get_backtest_trades
• get_confirmation_source
• get_confirmation_source_signals
• list_available_assets
• submit_backtest
• submit_backtest_batch
• submit_confirmation_source

Compare: most reliable data servers · most reliable ml servers

claude mcp add --transport http glimind https://glimind.com/mcp

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Emidlabs Backtest MCP server down right now?

As of 2026-10-20 03:00 UTC, the Emidlabs Backtest MCP server is up with a Glimind reliability score of 85/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 39 outages in 90 days, with a median recovery of 3 minutes.

How many tools does Emidlabs Backtest MCP server provide?

Emidlabs Backtest MCP server advertises 9 tools, including get_backtest_batch_results, get_backtest_result, get_backtest_trades, get_confirmation_source, get_confirmation_source_signals.

How do I install Emidlabs Backtest MCP server?

Point your MCP client at this streamable-http endpoint: https://mcp.backtest.emidlabs.com/mcp

Is the Emidlabs Backtest MCP server safe to connect to an AI agent?

Glimind scanned all 9 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Emidlabs Backtest MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.