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