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