validate_backtest — Canli Validation MCP Prompt
validate_backtest
is one of 8 prompts on the
Canli Validation
MCP server. Connect the server and it appears in your client, ready to invoke.
by client
How to invoke validate_backtest from your client
- Claude Code Canli Validation Prompt/validate_backtest run in your project directory
- Claude Desktop Canli Validation Prompt/validate_backtest ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Canli Validation Prompt/validate_backtest ~/.cursor/mcp.json
- VS Code Canli Validation Prompt/validate_backtest .vscode/mcp.json
- Zed Canli Validation Prompt/validate_backtest ~/.config/zed/settings.json
- Windsurf Canli Validation Prompt/validate_backtest ~/.codeium/windsurf/mcp_config.json
- Cline Canli Validation Prompt/validate_backtest ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Canli Validation Prompt/validate_backtest ~/.gemini/settings.json
- Grok Canli Validation Prompt/validate_backtest .mcp.json (in your project root)
- ChatGPT Canli Validation Prompt/validate_backtest Settings → Connectors → Advanced → Developer mode
- Claude.ai Canli Validation Prompt/validate_backtest Settings → Connectors → Add custom connector
- LangChain Canli Validation Prompt/validate_backtest pip install langchain-mcp-adapters
Other prompts on this server
Canli Validation also offers 4 resources — data you attach as context, where a prompt is something you run.
Read from the server itself, by connecting to it and calling prompts/list on 14 November 2026.
A listing does not declare its prompts, so asking is the only way to know them, and this
is what the server actually offers rather than what its listing claims. Names only are
stored; connect the server for each prompt's arguments.