Data Breach Notification Deadlines MCP server
io.github.Nero-Engine/breach-notification-deadlinesNero-Enginestreamable-httpv1.0.0Scanned
Who to notify after a data breach and by what date: all US states, SEC, HIPAA, GDPR, UK. Sourced.
3 tools: 1 do something that can't be undone and 2 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 1
- No findings
Tools listed without sign-in. Remote posture
Anlyon alternative
1 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →What the Data Breach Notification Deadlines MCP server can do
The Data Breach Notification Deadlines MCP server is published by the GitHub account Nero-Engine. It has 3 tools. It can do things that cannot be undone, such as sending, paying or publishing (who_to_notify), but cannot delete data. 2 tools only read.
1 tool can send data out of your system (who_to_notify).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 17, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
3 tools
Can't be undone 1Claude Code: ask
who_to_notifyWorks out every data breach notice a company owes and the deadline for each.Can send data outNo findings
Why it is in this group
- The name "who_to_notify" says "notify": a word for sending, and what is sent cannot be taken back.
What it can reach
- outboundThe name "who_to_notify" says "notify": it sends or publishes something to other people.
Description, as the server wrote it 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.
Only reads 2Show 2 read-only tools
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 offic…No findings
Why it is in this group
- The name "list_breach_laws" says "list": a word for reading.
Description, as the server wrote it 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_capabilitiesLists coverage (US states, US federal sector rules, countries), the date the data was last checked, and related Nero Labs Rules servers.No findings
Why it is in this group
- The name "list_capabilities" says "list": a word for reading.
Description, as the server wrote it Lists coverage (US states, US federal sector rules, countries), the date the data was last checked, and related Nero Labs Rules servers. Free.
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out1
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:25 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 1
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://breach-notification-deadlines.nerolabs.workers.dev/.well-known/oauth-protected-resource/mcp
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 irreversible). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://breach-notification-deadlines.nerolabs.workers.dev/mcp: tools/list returned 3 tools to an anonymous client, including who_to_notify (irreversible)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http breach-notification-deadlines https://breach-notification-deadlines.nerolabs.workers.dev/mcpclaude mcp add --transport http breach-notification-deadlines https://breach-notification-deadlines.nerolabs.workers.dev/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__breach-notification-deadlines__list_capabilities",
"mcp__breach-notification-deadlines__list_breach_laws"
],
"ask": [
"mcp__breach-notification-deadlines__who_to_notify"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as breach-notification-deadlines. Review it before you use it.
Capability tags behind 1 rule
- mcp__breach-notification-deadlines__who_to_notify outbound
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.Nero-Engine/breach-notification-deadlines/verify?hash=6c00c8728351751ad226c9610d1e53511ad96c8157a7263dab3e1a1b0e8c7c2d" | jq -e '.changed == false'Pinned hash 6c00c8728351, from Nov 17, 2026, 09:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.Nero-Engine/breach-notification-deadlines/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.Nero-Engine/breach-notification-deadlines)Source: MCP Registry. Synced Oct 21, 2026, 18:18 UTC.
Data Breach Notification Deadlines MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Data Breach Notification Deadlines MCP server safe?
- No scan can promise that. What its definitions show: 3 tools, 1 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Data Breach Notification Deadlines MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Data Breach Notification Deadlines MCP server do things that cannot be undone?
- Yes. 1 tool can send, pay, publish or merge: who_to_notify.
What tools does the Data Breach Notification Deadlines MCP server have?
- 3 tools: 1 irreversible, 2 read. who_to_notify, list_capabilities and list_breach_laws.
Does the Data Breach Notification Deadlines MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Data Breach Notification Deadlines MCP server send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): who_to_notify.
Has the Data Breach Notification Deadlines MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 17, 2026.