Data Breach Notification Deadlines
io.github.Nero-Engine/breach-notification-deadlinesVersion 1.0.0Who to notify after a data breach and by what date: all US states, SEC, HIPAA, GDPR, UK. Sourced.
Status
Responds152 msAnswered our handshake without sign-in.- Last checked
- Nov 14, 2026, 14:40 UTC
- Latency
- 152 ms
- Remotes responding
- 1 of 1
- Sign-in
- No sign-in
- Hosting
- Hosted outside the EU (detected)
- Registry data as of
- Nov 14, 2026, 22:14 UTC
Data from the official MCP Registry, checked by run.zero. How we check
Connect
Streamable HTTP
https://breach-notification-deadlines.nerolabs.workers.dev/mcpResponds152 msNo sign-in
Claude Code
claude mcp add --transport http breach-notification-deadlines https://breach-notification-deadlines.nerolabs.workers.dev/mcpClaude Desktop and claude.ai
Settings > Connectors > Add custom connector
Name: breach-notification-deadlines
Remote MCP server URL: https://breach-notification-deadlines.nerolabs.workers.dev/mcpCursor
{
"mcpServers": {
"breach-notification-deadlines": {
"url": "https://breach-notification-deadlines.nerolabs.workers.dev/mcp"
}
}
}VS Code
code --add-mcp '{"name":"breach-notification-deadlines","type":"http","url":"https://breach-notification-deadlines.nerolabs.workers.dev/mcp"}'Built your own server? run.zero hosts MCP servers on European infrastructure.
Tools
3 tools
Read-only | Idempotent | Open world | ||
|---|---|---|---|---|
list_breach_lawsLists 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. | Not declared | Not declared | Not declared | Not declared |
list_capabilitiesLists coverage (US states, US federal sector rules, countries), the date the data was last checked, and related Nero Labs Rules servers. Free. | Not declared | Not declared | Not declared | Not declared |
who_to_notifyWorks 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, email_address), whether the data was encrypted with the key kept safe, the date the breach was discovered, and flags: sec_registrant (US public company), sector (hipaa_covered_entity, hipaa_business_associate, glba_financial, health_app, nydfs_licensee) and role (owner, or service_provider holding data for another company). Returns each notice owed (people affected, state attorneys general, credit bureaus, HHS, SEC Form 8-K, FTC, EU and UK data protection authorities, Canada, Australia) with the deadline as a date where the law sets a fixed period, the deadline rule in words, what the notice must contain, how to send it and the official source, earliest first. Unclear cases give the SAFE answer (notice treated as required) plus what it depends on. Free. | Not declared | Not declared | Not declared | Not declared |
Details
- Registry status
- Active
- Published
- Oct 10, 2026
- Updated
- Oct 10, 2026
- Repository
- Not given
- Categories (suggested)
- CommunicationSuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
- GDPR
- Not declared