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