trader_state — Cipher — Bittensor Subnet Screener MCP Tool
trader_state
(trader state) is one of 8 tools on the
Cipher — Bittensor Subnet Screener
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call trader_state from your client
- Claude Code Cipher — Bittensor Subnet Screener trader_state run in your project directory
- Claude Desktop Cipher — Bittensor Subnet Screener trader_state ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Cipher — Bittensor Subnet Screener trader_state ~/.cursor/mcp.json
- VS Code Cipher — Bittensor Subnet Screener trader_state .vscode/mcp.json
- Zed Cipher — Bittensor Subnet Screener trader_state ~/.config/zed/settings.json
- Windsurf Cipher — Bittensor Subnet Screener trader_state ~/.codeium/windsurf/mcp_config.json
- Cline Cipher — Bittensor Subnet Screener trader_state ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Cipher — Bittensor Subnet Screener trader_state ~/.gemini/settings.json
- Grok Cipher — Bittensor Subnet Screener trader_state .mcp.json (in your project root)
- ChatGPT Cipher — Bittensor Subnet Screener trader_state Settings → Connectors → Advanced → Developer mode
- Claude.ai Cipher — Bittensor Subnet Screener trader_state Settings → Connectors → Add custom connector
- LangChain Cipher — Bittensor Subnet Screener trader_state pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http cipher https://mcp.brobotapp.com/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 10 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.