
Walk-Forward Validator
io.github.tylerscomic-labv1.0.0Updated Oct 2, 2026
Walk-Forward Efficiency, parameter-stability scoring, and WFO window generation.
Overview
Lets an assistant run walk-forward analysis on trading strategies: efficiency ratios, parameter-stability scoring, and rolling window generation.
- What it does
- Provides four tools for validating trading strategy optimizations. walk_forward_efficiency computes out-of-sample performance as a fraction of in-sample performance. parameter_stability_score rates a parameter surface as a robust plateau or a fragile spike. lock_after_wfo_check audits whether parameters were truly locked after optimization, and walk_forward_window_generator builds non-overlapping rolling in-sample and out-of-sample windows for a date range and step size.
- When to use it
- Useful when checking whether a strategy optimization generalizes to unseen data rather than being a curve fit, or when building walk-forward windows by hand is error-prone. Suited to quant and algo-trading validation workflows.
- Requirements
- Remote streamable HTTP endpoint; no authentication, environment variables, or headers declared. Self-hosting is possible from the source repository with Node.js and npm. Hosted use is described as having a free tier and a paid Pro tier for higher limits.
Installation
In SourceWeft
- Open Walk-Forward Validator in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"walkforward-validator-mcp": {
"type": "http",
"url": "https://walkforward-validator-mcp.mcpize.run/mcp"
}
}
}README
walkforward-validator-mcp
[License: MIT] [Live on MCPize]
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
walk_forward_efficiency
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.
parameter_stability_score
Scores a parameter surface for fragile curve-fit spikes vs. robust plateaus, flagging optimizations that only work at one exact parameter value.
lock_after_wfo_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.
walk_forward_window_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:
Part 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
Source: README.md at commit 13acca5
Tools
0Version history
1- v1.0.0LatestOct 2, 2026