check_exposure — data-breach-detector MCP Tool Read-only
check_exposure
(check exposure) 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 check_exposure from your client
- Claude Code data-breach-detector check_exposure run in your project directory
- Claude Desktop data-breach-detector check_exposure ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor data-breach-detector check_exposure ~/.cursor/mcp.json
- VS Code data-breach-detector check_exposure .vscode/mcp.json
- Zed data-breach-detector check_exposure ~/.config/zed/settings.json
- Windsurf data-breach-detector check_exposure ~/.codeium/windsurf/mcp_config.json
- Cline data-breach-detector check_exposure ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI data-breach-detector check_exposure ~/.gemini/settings.json
- Grok data-breach-detector check_exposure .mcp.json (in your project root)
- ChatGPT data-breach-detector check_exposure Settings → Connectors → Advanced → Developer mode
- Claude.ai data-breach-detector check_exposure Settings → Connectors → Add custom connector
- LangChain data-breach-detector check_exposure 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.