# Data Breach Notification Deadlines (remote · breach-notification-deadlines.nerolabs.workers.dev)

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

- Trust score: 59/100 (low)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-18

## Components

- remote · `breach-notification-deadlines.nerolabs.workers.dev`: 59/100 (this document), [markdown](https://verifymcp.io/servers/nero-engine-breach-notification-deadlines/breach-notification-deadlines.md), [page](https://verifymcp.io/servers/nero-engine-breach-notification-deadlines/breach-notification-deadlines)

## Channel facts

- Endpoint: `https://breach-notification-deadlines.nerolabs.workers.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-18.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 60/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 916 tokens (~305/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Data Breach Notification Deadlines MCP server?

Data Breach Notification Deadlines is a hosted endpoint at https://breach-notification-deadlines.nerolabs.workers.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http nero-engine-breach-notification-deadlines 'https://breach-notification-deadlines.nerolabs.workers.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "nero-engine-breach-notification-deadlines": {
      "url": "https://breach-notification-deadlines.nerolabs.workers.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "nero-engine-breach-notification-deadlines": {
      "type": "http",
      "url": "https://breach-notification-deadlines.nerolabs.workers.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.nero-engine-breach-notification-deadlines]
url = "https://breach-notification-deadlines.nerolabs.workers.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "nero-engine-breach-notification-deadlines": {
      "type": "remote",
      "url": "https://breach-notification-deadlines.nerolabs.workers.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add nero-engine-breach-notification-deadlines --url 'https://breach-notification-deadlines.nerolabs.workers.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  nero-engine-breach-notification-deadlines:
    url: "https://breach-notification-deadlines.nerolabs.workers.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "nero-engine-breach-notification-deadlines": {
      "Transport": "http",
      "Url": "https://breach-notification-deadlines.nerolabs.workers.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add nero-engine-breach-notification-deadlines -t streamable-http -u 'https://breach-notification-deadlines.nerolabs.workers.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "nero-engine-breach-notification-deadlines": {
      "type": "http",
      "url": "https://breach-notification-deadlines.nerolabs.workers.dev/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-18 (score 59, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-16 (score 58, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-13 (score 57, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-12 (score 56, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-11 (score 56)

First indexed and scored.

## MCP tools (3)

### `list_capabilities` (~39 tokens)

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` (~610 tokens)

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.

Input parameters:

- `affected` (array, required): 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…
- `data_types` (array): Personal data exposed, for example ["ssn","drivers_license","payment_card"]. If left out every law is treated as triggered (SAFE).
- `date_discovered` (string): Date the breach was discovered (or you became aware of it), YYYY-MM-DD. Defaults to today. Deadlines are counted from it.
- `encrypted` (boolean): 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.
- `materiality_date` (string): SEC registrants: date the company decided the incident is material, YYYY-MM-DD. The 8-K is due 4 business days after it.
- `role` (string): owner (default): the company that owns or licenses the data. service_provider: holds it for another company, which mostly means notifying that company quickly.
- `sec_registrant` (boolean): True for a company that files reports with the US SEC (listed in the US). Adds Form 8-K Item 1.05.
- `sector` (array): 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), nyd…

### `list_breach_laws` (~129 tokens)

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.

Input parameters:

- `country` (string): Optional country code or name, for example "GB", "Germany", "Canada".
- `scope` (string): Optional: us_state, us_federal_sector, country or region.
- `state` (string): Optional US state code or name.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/nero-engine-breach-notification-deadlines/breach-notification-deadlines#diagnostics

## Score history

- 2026-10-18: 59
- 2026-10-17: 58
- 2026-10-16: 58
- 2026-10-15: 57
- 2026-10-14: 57
- 2026-10-13: 57
- 2026-10-12: 56
- 2026-10-11: 56

## Common questions

### What is the Data Breach Notification Deadlines MCP server?

Data Breach Notification Deadlines is an MCP server listed in the public MCP registry as io.github.Nero-Engine/breach-notification-deadlines. Who to notify after a data breach and by what date: all US states, SEC, HIPAA, GDPR, UK. Sourced. This page covers its hosted endpoint (https://breach-notification-deadlines.nerolabs.workers.dev/mcp).

### Is the Data Breach Notification Deadlines MCP server safe to use?

Data Breach Notification Deadlines scores 59 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Data Breach Notification Deadlines MCP server expose?

Data Breach Notification Deadlines exposes 3 tools: list_capabilities, who_to_notify, list_breach_laws. Their descriptions and schemas cost roughly 778 tokens of context every time the server is loaded.

### Does the Data Breach Notification Deadlines MCP server require authentication?

No. We connected to Data Breach Notification Deadlines without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Data Breach Notification Deadlines MCP server still maintained?

Data Breach Notification Deadlines is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://breach-notification-deadlines.nerolabs.workers.dev/mcp
- Website: https://breach-notification-deadlines.nerolabs.workers.dev/
- Changelog RSS feed: https://verifymcp.io/servers/nero-engine-breach-notification-deadlines/breach-notification-deadlines.xml
- Changelog JSON feed: https://verifymcp.io/servers/nero-engine-breach-notification-deadlines/breach-notification-deadlines.json
- HTML version of this page: https://verifymcp.io/servers/nero-engine-breach-notification-deadlines/breach-notification-deadlines