English Français العربية

Walk-Forward Validator

Official registry Other

Walk-Forward Efficiency, parameter-stability scoring, and WFO window generation.

Source code Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code 
claude mcp add --transport http walk-forward-validator 'https://walkforward-validator-mcp.mcpize.run/mcp'
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "walk-forward-validator": {
            "type": "http",
            "url": "https://walkforward-validator-mcp.mcpize.run/mcp"
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. walkforward-validator-mcp
  2. The problem this solves
  3. Tools
  4. Use it
  5. Part of the AlgoForge suite
  6. License

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

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:

npm install
node server.js

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

Frequently asked questions

What is Walk-Forward Validator?

Walk-Forward Efficiency, parameter-stability scoring, and WFO window generation.

How do I install Walk-Forward Validator?

It runs as a remote server. In Claude Code: claude mcp add --transport http walk-forward-validator 'https://walkforward-validator-mcp.mcpize.run/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does Walk-Forward Validator need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is Walk-Forward Validator open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains Walk-Forward Validator?

It is published by tylerscomic-lab. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.