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