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