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