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