Data Breach Notification Deadlines
Server Details
Who to notify after a data breach and by what date: all US states, SEC, HIPAA, GDPR, UK. Sourced.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-06-18
- URL
TDQS
Score is being calculated.
Available Tools
3 toolslist_breach_lawsInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| scope | No | Optional: us_state, us_federal_sector, country or region. | |
| state | No | Optional US state code or name. | |
| country | No | Optional country code or name, for example "GB", "Germany", "Canada". |
list_capabilitiesInspect
Lists coverage (US states, US federal sector rules, countries), the date the data was last checked, and related Nero Labs Rules servers. Free.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
who_to_notifyInspect
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, 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.
| Name | Required | Description | Default |
|---|---|---|---|
| role | No | owner (default): the company that owns or licenses the data. service_provider: holds it for another company, which mostly means notifying that company quickly. | |
| sector | No | Sector rules that apply: hipaa_covered_entity, hipaa_business_associate, glba_financial (non-bank financial firms under the FTC Safeguards Rule), health_app (FTC Health Breach Notification Rule), nydfs_licensee (New York DFS regulated). | |
| affected | Yes | Where the affected people live: [{"state":"CA","count":1200},{"state":"TX","count":300},{"country":"Germany","count":40},{"country":"United Kingdom","count":15},{"country":"Canada","province":"Quebec","count":5}]. A bare two-letter code is read as a US state (CA = California); use {"country":"CA"} or "Canada" for Canada. | |
| encrypted | No | True only if all the exposed data was encrypted and the key was not exposed. Many US state laws then need no notice. Default false. | |
| data_types | No | Personal data exposed, for example ["ssn","drivers_license","payment_card"]. If left out every law is treated as triggered (SAFE). | |
| sec_registrant | No | True for a company that files reports with the US SEC (listed in the US). Adds Form 8-K Item 1.05. | |
| date_discovered | No | Date the breach was discovered (or you became aware of it), YYYY-MM-DD. Defaults to today. Deadlines are counted from it. | |
| materiality_date | No | SEC registrants: date the company decided the incident is material, YYYY-MM-DD. The 8-K is due 4 business days after it. |
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
3 tool updates
- First observed
list_breach_laws - First observed
list_capabilities - First observed
who_to_notify
Related MCP Connectors
Incident-reporting deadlines from the law: CRA, NIS2, DORA, GDPR, HIPAA, SEC 8-K. 6 of 9 tools free.
Bulk breach notice deadline checks: US states, SEC, HIPAA, GDPR, UK, per check billing via Apify.
1Indian cyber regulation register and incident-reporting deadlines (India, US, EU), read at source.
US federal and state cybersecurity/privacy law MCP server with cross-state comparison
Related MCP Servers
- AlicenseBqualityBmaintenanceMulti-regime AI incident classification and reporting MCP supporting EU AI Act Article 73, DORA, NIS2, and GDPR breach reporting.3MIT
- AlicenseAqualityAmaintenanceEnables AI assistants to answer questions offline, with no dependencies, about Gulf cyber incident notification duties, including which authorities to alert, their deadlines, and the official source behind each one.8MIT
- AlicenseNot gradedqualityDmaintenanceBroadcasts Article 73 incident reports simultaneously to EU AI Act, DORA, NIS2, GDPR, and ISO 42001 regulators, with escalation workflows and audit trails.52 PyPIMIT
- AlicenseAqualityDmaintenanceSource-verified regulatory and compliance intelligence: 10,000+ obligations across 39 pillars, each grounded in a primary legal source with a content hash. Covers the EU AI Act, GDPR, DORA, NIS2, HIPAA, Basel III and the MITRE ATT&CK/ATLAS families.251MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.