Skip to content

com.reglyze/mcp

by reglyze.com · remote · no sign-in to list tools · v1.1.0 · published by com.reglyze

NIS2 tools: scope check, EU transposition, incident deadlines, and your own org's status (token).

Changes · 3
CompareRegistry entry

7 tools: 3 change things and 4 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http reglyze https://api.reglyze.com/mcp

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

7 tools

Changes things 3Claude Code: ask
  • incident_deadline_formatsNIS2 incident-notification deadlines for a country: the 24h/72h/1-month stages with their national legal basis, the competent authority/CSIRT and portal, and the national severity …No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    NIS2 incident-notification deadlines for a country: the 24h/72h/1-month stages with their national legal basis, the competent authority/CSIRT and portal, and the national severity vocabulary (e.g. Italy's ACN IS-1..IS-4 typologies, with their entity-class applicability).
  • open_tasksRequires a Reglyze API token.No findings

    Why it is in this group

    • The name "open_tasks" says "open": a word for a change.
    Description, as the server wrote it
    Requires a Reglyze API token. Lists YOUR organization's open remediation tasks. Optional filters: status, severity, overdue.
  • scope_checkDetermine whether NIS2 (and its national transposition) applies to an organization, and whether it is an essential or important entity.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Determine whether NIS2 (and its national transposition) applies to an organization, and whether it is an essential or important entity. Inputs: EU/EEA country (ISO-2), primary NIS2 sector, headcount, turnover/balance sheet in M EUR, special categories (DNS, TLD, cloud, qualified trust services). Returns classification, reasoning, the national transposition law with its deviations, and next-step links.
Only reads 4Claude Code: allow
  • compliance_statusRequires a Reglyze API token.No findings

    Why it is in this group

    • The name "compliance_status" says "status": a word for reading.
    Description, as the server wrote it
    Requires a Reglyze API token. Returns YOUR organization's current compliance score, implementation/documentation sub-scores, open-task counts, and the national-framework per-objective view.
  • documents_listRequires a Reglyze API token.No findings

    Why it is in this group

    • The name "documents_list" says "list": a word for reading.
    Description, as the server wrote it
    Requires a Reglyze API token. Lists YOUR organization's compliance documents (title, type, status, current version). Metadata only, not document content.
  • incidents_listRequires a Reglyze API token.No findings

    Why it is in this group

    • The name "incidents_list" says "list": a word for reading.
    Description, as the server wrote it
    Requires a Reglyze API token. Lists YOUR organization's recorded incidents (title, status, severity, detection date).
  • transposition_statusCurrent NIS2 transposition status per EU/EEA country (law, stage, competent authority, sources), from the Reglyze transposition tracker (curated + weekly auto-updated).No findings

    Why it is in this group

    • The name "transposition_status" says "status": a word for reading.
    Description, as the server wrote it
    Current NIS2 transposition status per EU/EEA country (law, stage, competent authority, sources), from the Reglyze transposition tracker (curated + weekly auto-updated). Omit the country for the full map.

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.

Install

Pinned to version 1.1.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http reglyze https://api.reglyze.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__reglyze__transposition_status",
      "mcp__reglyze__compliance_status",
      "mcp__reglyze__documents_list",
      "mcp__reglyze__incidents_list"
    ],
    "ask": [
      "mcp__reglyze__scope_check",
      "mcp__reglyze__incident_deadline_formats",
      "mcp__reglyze__open_tasks"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as reglyze. Review it before you use it.