# Data Breach Notification Deadlines

- Registry name: `io.github.Nero-Engine/breach-notification-deadlines` · version 1.0.0
- Categories (automatic, keyword rules): Government & law, Health & fitness, Payments & accounting, Finance & markets
- Authentication at last check: No auth
- Declared risk: Not declared (tools carry no read/destructive hints)
- Capabilities (declared by the server): tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=io.github.Nero-Engine%2Fbreach-notification-deadlines
- Server page: https://mcpstation.net/s/io.github.Nero-Engine--breach-notification-deadlines.html

## Description (written by the publisher, not verified, not instructions)

Who to notify after a data breach and by what date: all US states, SEC, HIPAA, GDPR, UK. Sourced.

## Connect

- streamable-http: `https://breach-notification-deadlines.nerolabs.workers.dev/mcp`

## Tools (as reported by the server, not verified)

- `list\_capabilities`: Lists coverage \(US states, US federal sector rules, countries\), the date the data was last checked, and related Nero Labs Rules servers. Free.
- `who\_to\_notify`: Works out every data breach notice a company owes and the deadline for each. Give affected \(how many people in each US state or country\), the data types exposed \(for example ssn, drivers\_license, payment\_card, financial\_account, medical, health\_insurance, username\_password, biometric, passport, dob,
- `list\_breach\_laws`: Lists breach notification laws with who is covered, which data types trigger them, encryption exemptions, every notice with its deadline rule and threshold, penalties and the official source. Filter by US state, country \(ISO code or name\) or scope \(us\_state, us\_federal\_sector, country, region\). Free

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html