nerolabs-breach-notification-deadlines

endpoint

https://breach-notification-deadlines.nerolabs.workers.dev/mcp

protocol

streamable-http ·2025-06-18

authentication

none observed

public key

none — nobody has proven they own this listing · is it yours? claim it

karma

0 · newcomer

Is nerolabs-breach-notification-deadlines live?

Yes — it answered the hub's last check (checked 42m ago). It answered 100% of checks over the last 30 days.

Is nerolabs-breach-notification-deadlines free to use?

Yes — the hub reached it with no key and no payment.

What tools does nerolabs-breach-notification-deadlines have?

3 tools: who_to_notify, list_capabilities, list_breach_laws.

Is nerolabs-breach-notification-deadlines safe to connect?

The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

• list_capabilities open 42m ago

  Lists coverage (US states, US federal sector rules, countries), the date the data was last checked, and related Nero Labs Rules servers. Free.

  mcp-tool

  12345

  {
    "type": "object",
    "properties": {},
    "additionalProperties": false
  }

  arguments 5 lines copy
• list_breach_laws open 42m ago

  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.

  mcp-tool

  123456789101112131415161718

  {
    "type": "object",
    "properties": {
      "scope": {
        "type": "string",
        "description": "Optional: us_state, us_federal_sector, country or region."
      },
      "state": {
        "type": "string",
        "description": "Optional US state code or name."
      },
      "country": {
        "type": "string",
        "description": "Optional country code or name, for example \"GB\", \"Germany\", \"Canada\"."
      }
    },
    "additionalProperties": false
  }

  arguments 18 lines copy
• who_to_notify unknown never probed

  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.

  mcp-tool

  123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263

  {
    "type": "object",
    "required": [
      "affected"
    ],
    "properties": {
      "role": {
        "enum": [
          "owner",
          "service_provider"
        ],
        "type": "string",
        "description": "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": {
        "type": "array",
        "items": {
          "enum": [
            "hipaa_covered_entity",
            "hipaa_business_associate",
            "glba_financial",
            "health_app",
            "nydfs_licensee",
            "telecom",
            "critical_infrastructure"
          ],
          "type": "string"
        },
        "description": "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": {
        "type": "array",
        "items": {
          "type": "object"
        },
        "description": "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": {
        "type": "boolean",
        "description": "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": {
        "type": "array",
        "items": {
          "type": "string"
        },
        "description": "Personal data exposed, for example [\"ssn\",\"drivers_license\",\"payment_card\"]. If left out every law is treated as triggered (SAFE)."
      },
      "sec_registrant": {
        "type": "boolean",
        "description": "True for a company that files reports with the US SEC (listed in the US). Adds Form 8-K Item 1.05."
      },
      "date_discovered": {
        "type": "string",
        "description": "Date the breach was discovered (or you became aware of it), YYYY-MM-DD. Defaults to today. Deadlines are counted from it."
      },
      "materiality_date": {
        "type": "string",
        "description": "SEC registrants: date the company decided the incident is material, YYYY-MM-DD. The 8-K is due 4 business days after it."
      }
    },
    "additionalProperties": false
  }

  arguments 63 lines copy

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.