Data Breach Notification Deadlines

Name: Data Breach Notification Deadlines
Author: Nero-Engine

MCP serverMCP

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

by Nero-Enginehomepage ↗v1.0.0

Is this yours?

This record is unclaimed

Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.

Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"data-breach-notification-deadlines","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.

Claim this record

Observed by Wellknown

Evidence

Everything here was measured by our prober or read from a registry. Nothing is self-reported.

30-day availability37/37 checks ok

when	check	result	http	latency	detail
4 h ago	mcp initialize	ok	200	73 ms	server nerolabs-breach-notification-deadlines 1.0.0 · protocol 2025-06-18 · 3 tools
10 h ago	mcp initialize	ok	200	86 ms	server nerolabs-breach-notification-deadlines 1.0.0 · protocol 2025-06-18 · 3 tools
17 h ago	mcp initialize	ok	200	10 ms	server nerolabs-breach-notification-deadlines 1.0.0 · protocol 2025-06-18 · 3 tools
24 h ago	mcp initialize	ok	200	69 ms	server nerolabs-breach-notification-deadlines 1.0.0 · protocol 2025-06-18 · 3 tools
34 h ago	mcp initialize	ok	200	69 ms	server nerolabs-breach-notification-deadlines 1.0.0 · protocol 2025-06-18 · 3 tools
2 d ago	mcp initialize	ok	200	54 ms	server nerolabs-breach-notification-deadlines 1.0.0 · protocol 2025-06-18 · 3 tools
2 d ago	mcp initialize	ok	200	49 ms	server nerolabs-breach-notification-deadlines 1.0.0 · protocol 2025-06-18 · 3 tools
2 d ago	mcp initialize	ok	200	28 ms	server nerolabs-breach-notification-deadlines 1.0.0 · protocol 2025-06-18 · 3 tools
3 d ago	mcp initialize	ok	200	67 ms	server nerolabs-breach-notification-deadlines 1.0.0 · protocol 2025-06-18 · 3 tools
3 d ago	mcp initialize	ok	200	41 ms	server nerolabs-breach-notification-deadlines 1.0.0 · protocol 2025-06-18 · 3 tools

Tools observed via MCP handshake

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
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, pen

Declared by sources

What the publisher says

Attributed to the source that supplied each field. Treated as claims, not facts.

No long description beyond the summary.

kind Official MCP Registry

name Official MCP Registry

summary Official MCP Registry

version Official MCP Registry

description Official MCP Registry

homepageUrl Official MCP Registry

publisherName Official MCP Registry

Provenance

Where this record came from

Every source is kept verbatim. Field changes are logged as events.

Official MCP Registryio.github.Nero-Engine/breach-notification-deadlines

first seen 10 d ago · fetched 7 h agoopen ↗

Field history (6 recent events)

10 d ago · declared · summary → "Who to notify after a data breach and by what date: all US states, SEC, HIPAA, GDPR, UK. Sourced."
10 d ago · declared · description → "Who to notify after a data breach and by what date: all US states, SEC, HIPAA, GDPR, UK. Sourced."
10 d ago · declared · publisherName → "Nero-Engine"
10 d ago · declared · homepageUrl → "https://breach-notification-deadlines.nerolabs.workers.dev/"
10 d ago · declared · version → "1.0.0"
10 d ago · declared · protocols → ["mcp"]

This record is unclaimed

Evidence

What the publisher says

Capabilities

Where this record came from