Backtest Cost Sensitivity MCP server
not respondingCommission/slippage sensitivity sweep, breakeven cost finder, and lookahead-bias checklist.
0 stars
Reviews
Write oneNobody has reviewed Backtest Cost Sensitivity yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Backtest Cost Sensitivity tools
Tool list not cached yet. `describe` through the gateway fetches it live.
Public scan report
scanner v0.1.10 · 2026-10-28 · same rubric, same numbers if you re-run it
- –Code scanremote-only server, no package to scann/a
- Live reliabilityremote unreachable: HTTP 5000/20
- –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
- Auth qualityno auth information5/15
- Maintenancelast push 93 days ago8/15
- Maintainer identityregistry namespace matches repository owner6/10
Findings (1)
- highRemote endpoint did not respond
reliability.unreachableHTTP 500
How Backtest Cost Sensitivity compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 32/100
- higher than 6% of 48,255 servers
- Uptime
- 18%
- of our recent checks; the typical remote server answers 100%
- Response time
- 266 ms
- faster than 53% of 30,031 servers
Install Backtest Cost Sensitivity in Claude Code, Cursor or VS Code
claude mcp add --transport http backtest-cost-sensitivity-mcp https://backtest-cost-sensitivity-mcp.mcpize.run/mcp
What the publisher says
From the Backtest Cost Sensitivity repository's README, as published. We do not edit it. Read it on GitHub
backtest-cost-sensitivity-mcp
An MCP server that sweeps commission and slippage assumptions across a backtest to find the real breakeven cost per trade, plus a structured look-ahead-bias audit.
The problem this solves
Most backtests run with one fixed commission/slippage assumption, which hides how fragile a strategy's edge actually is to real-world execution costs. A strategy that's profitable at 0.5 ticks of slippage and dead at 1.5 ticks needs to know that before going live, not after.
Tools
costsensitivitysweep
Sweeps a range of commission and slippage assumptions against backtest results and reports how performance metrics degrade across the range.
breakevencostfinder
Finds the exact commission/slippage level at which a strategy's edge goes to zero — the real cost ceiling, not a guess.
lookaheadbiaschecklist
A structured audit for the specific look-ahead-bias patterns that inflate backtest performance (data leakage across bar boundaries, repainting indicators, future-bar reads).
Use it
Hosted (recommended): MCPize — free tier, paid Pro tier for higher limits.
Self-host:
npm install
node server.jsPart of the AlgoForge suite
Prop-firm and quant-validation tools for algo traders: prop-rules-mcp, trade-journal-mcp, payout-calc-mcp, econ-calendar-mcp, montecarlo-validator-mcp, overfitting-audit-mcp, walkforward-validator-mcp, pinescript-audit-mcp, pinescript-mcp.
License
MIT
Nothing above is checked by us. What we check is on the safety report.
Grade history
- 2026-10-28revokeA → Fscore 32: Remote endpoint did not respond
Backtest Cost Sensitivity: common questions
- Is Backtest Cost Sensitivity MCP server safe?
- No: it is graded F and blocked at the gateway (32/100). Read the Backtest Cost Sensitivity safety report
- How do I install Backtest Cost Sensitivity?
- It runs remotely at backtest-cost-sensitivity-mcp.mcpize.run. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does Backtest Cost Sensitivity need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Backtest Cost Sensitivity maintained?
- The last commit was 100 days ago (2026-07-27). The latest release is v1.0.0.
- Is Backtest Cost Sensitivity up?
- 18% of our last 28 checks got an answer. We check remote servers about four times a day.
- How does Backtest Cost Sensitivity compare with other MCP servers?
- safety score 32/100 (higher than 6% of 48,255 servers); uptime 18% (of our recent checks; the typical remote server answers 100%); response time 266 ms (faster than 53% of 30,031 servers). Full comparison.