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