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