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