validate_track_record — Canli Validation MCP Tool
validate_track_record
(validate track record) is one of 18 tools on the
Canli Validation
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call validate_track_record from your client
- Claude Code Canli Validation validate_track_record run in your project directory
- Claude Desktop Canli Validation validate_track_record ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Canli Validation validate_track_record ~/.cursor/mcp.json
- VS Code Canli Validation validate_track_record .vscode/mcp.json
- Zed Canli Validation validate_track_record ~/.config/zed/settings.json
- Windsurf Canli Validation validate_track_record ~/.codeium/windsurf/mcp_config.json
- Cline Canli Validation validate_track_record ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Canli Validation validate_track_record ~/.gemini/settings.json
- Grok Canli Validation validate_track_record .mcp.json (in your project root)
- ChatGPT Canli Validation validate_track_record Settings → Connectors → Advanced → Developer mode
- Claude.ai Canli Validation validate_track_record Settings → Connectors → Add custom connector
- LangChain Canli Validation validate_track_record pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http canli-validation-mcp https://canlicapital.com/mcpOther tools on this server
- validate_deflated_sharpe
- validate_overfitting
- validate_reality_check
- validate_paper_evidence
- validate_breadth
- validate_backtest_length
- validate_haircut_sharpe
- validate_luck_trials
- audit_backtest
- verify_receipt
- service_status
- backtest_strategy
- summarize_series
- stress_test
- check_feasibility
- check_leakage
- placebo_test
This list was read from the server itself, by connecting to it and calling tools/list on 14 November 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.