get_latest_signal — Backtest360 MCP Tool Read-only
get_latest_signal
(get latest signal) is one of 20 tools on the
Backtest360
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_latest_signal from your client
- Claude Code Backtest360 get_latest_signal run in your project directory
- Claude Desktop Backtest360 get_latest_signal ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Backtest360 get_latest_signal ~/.cursor/mcp.json
- VS Code Backtest360 get_latest_signal .vscode/mcp.json
- Zed Backtest360 get_latest_signal ~/.config/zed/settings.json
- Windsurf Backtest360 get_latest_signal ~/.codeium/windsurf/mcp_config.json
- Cline Backtest360 get_latest_signal ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Backtest360 get_latest_signal ~/.gemini/settings.json
- Grok Backtest360 get_latest_signal .mcp.json (in your project root)
- ChatGPT Backtest360 get_latest_signal Settings → Connectors → Advanced → Developer mode
- Claude.ai Backtest360 get_latest_signal Settings → Connectors → Add custom connector
- LangChain Backtest360 get_latest_signal pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http backtest360 https://mcp.backtest360.com/mcpOther tools on this server
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.