io.github.Nero-Engine/breach-notification-deadlines

Est-ce que io.github.Nero-Engine/breach-notification-deadlines est sûr ?

Au dernier audit MCP Hub, le serveur MCP « io.github.Nero-Engine/breach-notification-deadlines » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 3 outils

• list_breach_laws≈ 185 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.

  Paramètres, retour & exemple (3)

  Paramètres

  • scope · string · optionnel
    Optional: us_state, us_federal_sector, country or region.
  • state · string · optionnel
    Optional US state code or name.
  • country · string · optionnel
    Optional country code or name, for example "GB", "Germany", "Canada".

  Exemple d'appel

  {"name": "list_breach_laws", "arguments": {"scope": "texte", "state": "texte", "country": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_capabilities≈ 68 tokens

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

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "list_capabilities", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• who_to_notify≈ 820 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.

  Paramètres, retour & exemple (8)

  Paramètres

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

  Exemple d'appel

  {"name": "who_to_notify", "arguments": {"affected": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

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