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