Nis2 Incident Runbook Lint MCP server
Reads your incident-response runbook and says which of the three Article 23 clocks it gets wrong
A89/100grade A
Adoption
Growing
0 stars398 downloads/wk
Reviews
Write oneNobody has reviewed Nis2 Incident Runbook Lint yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Nis2 Incident Runbook Lint tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.5 · 2026-09-19 · same rubric, same numbers if you re-run it
no findings
- Code scan6 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 0 days ago15/15
- Maintainer identityregistry namespace matches repository owner6/10
Overall 89/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON
Install directly
Runs npx -y @readystack/nis2-incident-runbook-lint on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add nis2-incident-runbook-lint -- npx -y @readystack/nis2-incident-runbook-lint
Nis2 Incident Runbook Lint: common questions
- Is Nis2 Incident Runbook Lint MCP server safe?
- Yes, by our scan: it is graded A (89/100). Read the Nis2 Incident Runbook Lint safety report
- How do I install Nis2 Incident Runbook Lint?
- It runs on your machine. Copy the Claude Code, Claude Desktop or Cursor config from the install section.
- Does Nis2 Incident Runbook Lint need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Nis2 Incident Runbook Lint maintained?
- The last commit was in the last day (2026-09-19). The latest release is v1.0.3.