Search / io.github.Nero-Engine/breach-notification-deadlines
protogridR0· no sign-inWho to notify after a data breach and by what date: all US states, SEC, HIPAA, GDPR, UK. Sourced.
v1.0.0 · active · website · descriptor JSON · versions
{
"mcpServers": {
"breach-notification-deadlines": {
"type": "http",
"url": "https://breach-notification-deadlines.nerolabs.workers.dev/mcp"
}
}
}claude mcp add --transport http breach-notification-deadlines https://breach-notification-deadlines.nerolabs.workers.dev/mcp[mcp_servers.breach-notification-deadlines]
url = "https://breach-notification-deadlines.nerolabs.workers.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"breach-notification-deadlines": {
"type": "remote",
"url": "https://breach-notification-deadlines.nerolabs.workers.dev/mcp",
"enabled": true
}
}
}{
"mcpServers": {
"breach-notification-deadlines": {
"type": "http",
"url": "https://breach-notification-deadlines.nerolabs.workers.dev/mcp"
}
},
"deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=breach-notification-deadlines&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vYnJlYWNoLW5vdGlmaWNhdGlvbi1kZWFkbGluZXMubmVyb2xhYnMud29ya2Vycy5kZXYvbWNwIn0%3D"
}{
"servers": {
"breach-notification-deadlines": {
"type": "http",
"url": "https://breach-notification-deadlines.nerolabs.workers.dev/mcp"
}
}
}{
"mcpServers": {
"breach-notification-deadlines": {
"httpUrl": "https://breach-notification-deadlines.nerolabs.workers.dev/mcp"
}
}
}extensions:
"breach-notification-deadlines":
enabled: true
name: "breach-notification-deadlines"
type: streamable_http
uri: "https://breach-notification-deadlines.nerolabs.workers.dev/mcp"
timeout: 300
protocol.modernnewest supported version is 2025-06-18; 2026-07-28 not supported, older versions are deprecated until 2027-07-28protocol.statelessonly applies to 2026-07-28 serversprotocol.transportstreamable HTTPprotocol.list_ttlonly applies to 2026-07-28 serversauth.prm, auth.as_metadata, auth.cimdno remote uses OAuthauth.secret_in_urlno templated URLtools.descriptionsevery tool has a descriptiontools.description_length1 tools have descriptions over 1,024 characters, which crowds the contexttools.schemasevery tool has an object input schematools.annotationsno tool declares readOnlyHint or destructiveHint, so clients cannot tell safe calls from risky onestools.directory_hintsno tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: who_to_notify (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); list_breach_laws (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); list_capabilities (readOnlyHint, destructiveHint, idempotentHint, openWorldHint)tools.token_costabout 1,018 tokens to load every tooltools.api_dumptools are not a one-to-one API dumpstability.changesno tool changes in 30 daysstability.rug_pullno tool changed its meaning under the same namedeps.known_vulns, deps.mcp_sdk_version, deps.resolvableno npm or PyPI packageNo tool definition changes recorded. A server's first observation is its baseline; later probes record what changes.
Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.
+website +reachable +uptime-95% +updated-10d-ago -no-repository
Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.
| remote | auth | reachable | uptime 30d | p50 | protocol | last ok |
|---|---|---|---|---|---|---|
https://breach-notification-deadlines.nerolabs.workers.dev/mcp streamable-http | none | yes | 95% | 161 ms | 2025-06-18 | 2026-10-20 |
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. |
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, 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. |
Schemas: list_tools.
And 50 more from this publisher.
{
"name": "io.github.Nero-Engine/breach-notification-deadlines",
"title": "Data Breach Notification Deadlines",
"$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
"remotes": [
{
"url": "https://breach-notification-deadlines.nerolabs.workers.dev/mcp",
"type": "streamable-http"
}
],
"version": "1.0.0",
"websiteUrl": "https://breach-notification-deadlines.nerolabs.workers.dev/",
"description": "Who to notify after a data breach and by what date: all US states, SEC, HIPAA, GDPR, UK. Sourced."
}