Claude Code Backtest360 get_latest_signal
How to: Claude Code Backtest360 get_latest_signal
Add Backtest360 to Claude Code
-
01
Run this in your project directory.
claude mcp add --transport http backtest360 https://mcp.backtest360.com/mcp-
02
Restart your session so the server is picked up.
-
03
Ask for something get_latest_signal does. Claude Code lists the server's tools on connect and calls get_latest_signal itself — you do not invoke it by name.
-
04
If nothing happens, check the server is running and that Backtest360's identifier in your config matches the one above exactly.
Adds it for this project only. Append --scope user to make it available everywhere. Claude Code docs
Set these first
Backtest360 will not start until these are set, so get_latest_signal never becomes available.
-
BACKTEST360_API_KEY
Same tool, other clients
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 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.