Walk-Forward Validator MCP server
not respondingWalk-Forward Efficiency, parameter-stability scoring, and WFO window generation.
0 stars
Reviews
Write oneNobody has reviewed Walk-Forward Validator yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Walk-Forward Validator 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 Walk-Forward Validator 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
- 419 ms
- faster than 35% of 30,031 servers
Install Walk-Forward Validator in Claude Code, Cursor or VS Code
claude mcp add --transport http walkforward-validator-mcp https://walkforward-validator-mcp.mcpize.run/mcp
What the publisher says
From the Walk-Forward Validator repository's README, as published. We do not edit it. Read it on GitHub
walkforward-validator-mcp
An MCP server for walk-forward analysis of trading strategies — Walk-Forward Efficiency ratio, parameter-stability scoring, lock-after-optimization audits, and WFO window generation.
The problem this solves
A strategy optimized on one historical window and never re-validated on a fresh, unseen window is a curve fit until proven otherwise. Walk-forward analysis is the standard fix, but building the rolling windows correctly and scoring whether a parameter surface is a robust plateau or a fragile spike is easy to get subtly wrong by hand.
Tools
walkforwardefficiency
Computes the Walk-Forward Efficiency ratio — out-of-sample performance as a fraction of in-sample performance — the core signal for whether an optimization generalizes.
parameterstabilityscore
Scores a parameter surface for fragile curve-fit spikes vs. robust plateaus, flagging optimizations that only work at one exact parameter value.
lockafterwfo_check
Audits whether parameters were genuinely locked after the walk-forward optimization step, or quietly re-tuned against the "out-of-sample" data — the mistake that silently invalidates a WFO result.
walkforwardwindow_generator
Generates correctly non-overlapping rolling in-sample/out-of-sample windows for a given date range and step size.
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, pinescript-audit-mcp, backtest-cost-sensitivity-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
Walk-Forward Validator: common questions
- Is Walk-Forward Validator MCP server safe?
- No: it is graded F and blocked at the gateway (32/100). Read the Walk-Forward Validator safety report
- How do I install Walk-Forward Validator?
- It runs remotely at walkforward-validator-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 Walk-Forward Validator need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Walk-Forward Validator maintained?
- The last commit was 100 days ago (2026-07-27). The latest release is v1.0.0.
- Is Walk-Forward Validator up?
- 18% of our last 28 checks got an answer. We check remote servers about four times a day.
- How does Walk-Forward Validator 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 419 ms (faster than 35% of 30,031 servers). Full comparison.