mcp-registry/com.backtest360/backtest360 · v0.2.4
As of 2026-10-26 21:09 UTC, the Backtest360 MCP server is up with a Glimind reliability score of 88/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 8 outages in 90 days, with a median recovery of 7 minutes.
MCP server exposing the Backtest360 engine API as tools for AI agents.
Point your MCP client at this streamable-http endpoint: https://mcp.backtest360.com/mcp
20 of 20 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
51 parameter(s) across 17 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
1 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 17 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.backtest360%2Fbacktest360/fixes
{
"name": "compare_backtests",
"description": "Run several strategies on the same data and compare side by side.\n\n One quota-counted call, but compute scales with the number of\n strategies. If the wall-clock compute budget is exceeded, the call\n fails with a tool error (504) instead of returning partial results —\n narrow the request (fewer strategies, shorter date range, coarser\n frequency) and retry.\n\n Args:\n data_source: Shared data source (same shape as run_backtest).\n strate",
"inputSchema": {
"type": "object",
"title": "compare_backtestsArguments",
"required": [
"data_source",
"strategies"
],
"properties": {
"strategies": {
"type": "array",
"items": {
"type": "object",
"additionalProperties": true
},
"title": "Strategies"
},
"data_source": {
"type": "object",
"title": "Data Source",
"additionalProperties": true
},
"trades_limit": {
"type": "integer",
"title": "Trades Limit",
"default": 50
},
"response_detail": {
"enum": [
"summary",
"stats",
"full"
],
"type": "string",
"title": "Response Detail",
"default": "summary"
},
"include_benchmark": {
"type": "boolean",
"title": "Include Benchmark",
"default": false
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "compute_stats",
"description": "Compute the engine's performance metrics from a returns series.\n\n Use when the returns came from somewhere\n other than run_backtest (an external system, a portfolio) — backtest\n results already include these statistics.\n\n Args:\n returns: Per-bar log returns as {\"dates\": [...], \"values\": [...]}\n parallel arrays (ISO-8601 dates).\n trading_days_per_year: Required annualization factor — 252 for a\n daily equities calendar",
"inputSchema": {
"type": "object",
"title": "compute_statsArguments",
"required": [
"returns",
"trading_days_per_year"
],
"properties": {
"trades": {
"anyOf": [
{
"type": "array",
"items": {
"type": "object",
"additionalProperties": true
}
},
{
"type": "null"
}
],
"title": "Trades",
"default": null
},
"returns": {
"type": "object",
"title": "Returns",
"additionalProperties": true
},
"risk_free_rate": {
"type": "number",
"title": "Risk Free Rate",
"default": 0
},
"benchmark_returns": {
"anyOf": [
{
"type": "object",
"additionalProperties": true
},
{
"type": "null"
}
],
"title": "Benchmark Returns",
"default": null
},
"trading_days_per_year": {
"type": "integer",
"title": "Trading Days Per Year"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "engine_info",
"description": "Engine version, API contract number, and health.\n\n Free (not quota-counted). Call once at the start of a session\n to confirm the engine is reachable and which contract it serves.\n ",
"inputSchema": {
"type": "object",
"title": "engine_infoArguments",
"properties": {}
},
"annotations": {
"readOnlyHint": true
}
}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/com.backtest360/backtest360"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.backtest360/backtest360"}) over MCP.
run_backtest ~457 tokenscompute_stats ~328 tokenscompare_backtests ~316 tokensexport_backtest ~263 tokensget_price_history ~251 tokensStatic 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:
[](https://glimind.com/server/mcp-registry%2Fcom.backtest360%2Fbacktest360?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.backtest360%2Fbacktest360?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.backtest360%2Fbacktest360.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.backtest360%2Fbacktest360.svg :target: https://glimind.com/server/mcp-registry%2Fcom.backtest360%2Fbacktest360?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:7243cece6067c9ff…, first seen 2026-10-17, included at leaf 5014 of 75,464. Version history · verify what your client received.
Compare: most reliable finance servers · most reliable data servers · most reliable other servers · most reliable knowledge servers · most reliable security servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-26 21:09 UTC, the Backtest360 MCP server is up with a Glimind reliability score of 88/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 8 outages in 90 days, with a median recovery of 7 minutes.
Backtest360 MCP server advertises 20 tools, including compare_backtests, compute_stats, engine_info, export_backtest, get_catalog.
Point your MCP client at this streamable-http endpoint: https://mcp.backtest360.com/mcp
Glimind scanned all 20 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.
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.