Claude Desktop Canli Validation validate_backtest_length
How to: Claude Desktop Canli Validation validate_backtest_length
Add Canli Validation to Claude Desktop
-
01
Open ~/Library/Application Support/Claude/claude_desktop_config.json and merge this in. Keep any servers already there.
{
"mcpServers": {
"canli-validation-mcp": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://canlicapital.com/mcp"
]
}
}
}-
02
Save the file and restart Claude Desktop.
-
03
Ask for something validate_backtest_length does. Claude Desktop lists the server's tools on connect and calls validate_backtest_length itself — you do not invoke it by name.
-
04
If nothing happens, check the server is running and that Canli Validation's identifier in your config matches the one above exactly.
Claude Desktop has no remote transport in its config file, so this bridges through mcp-remote. Restart the app after saving. Claude Desktop docs
Set these first
Canli Validation will not start until these are set, so validate_backtest_length never becomes available.
-
CANLI_KEY -
CANLI_LOCAL -
CANLI_API_BASE
Same tool, other clients
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.