Data Breach Notification Deadlines

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

사용해야 할까요

품질 및 안전성

A
설명 품질
100%
스키마 완전성
73%
이름 품질
93%
오염 위험
100%
권한 일치
100%
프로토콜 준수
100%

도구 정의와 프로토콜 준수에 대한 자동 분석을 기반으로 합니다.

컨텍스트 비용

~948토큰 (도구 정의)
~2.4 KB일반적인 응답 크기
중간 정도의 주의 영향 (128k 컨텍스트의 0.74%)

이는 서버의 도구가 모델의 컨텍스트에 로드될 때마다 소비되는 대략적인 토큰 수입니다. 수치가 높을수록 다른 작업에 사용할 수 있는 주의가 줄어듭니다.

설치

원클릭 설치

`claude_desktop_config.json` 파일에 다음을 추가하세요:

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

원격 엔드포인트

https://breach-notification-deadlines.nerolabs.workers.dev/mcpstreamable-http

할 수 있는 일

도구 목록

도구 (3)

🟢 읽기 전용🟡 쓰기🔴 삭제⚪ 알 수 없음
🟢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.

입력 스키마

{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
🟡who_to_notify(affected, data_types, encrypted, date_discovered, sec_registrant, ...)

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.

입력 스키마

{
  "type": "object",
  "properties": {
    "affected": {
      "type": "array",
      "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.",
      "items": {
        "type": "object"
      }
    },
    "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)."
    },
    "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."
    },
    "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."
    },
    "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."
    },
    "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."
    },
    "sector": {
      "type": "array",
      "items": {
        "type": "string",
        "enum": [
          "hipaa_covered_entity",
          "hipaa_business_associate",
          "glba_financial",
          "health_app",
          "nydfs_licensee",
          "telecom",
          "critical_infrastructure"
        ]
      },
      "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)."
    },
    "role": {
      "type": "string",
      "enum": [
        "owner",
        "service_provider"
      ],
      "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."
    }
  },
  "required": [
    "affected"
  ],
  "additionalProperties": false
}
🟢list_breach_laws(state, country, scope)

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.

입력 스키마

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

커뮤니티

이 서버 평가하기

증거

최근 관측

검증됨버전이 기록되지 않음도구 3개