Nis2 Incident Runbook Lint MCP server

by jmshinhwa·io.github.jmshinhwa/nis2-incident-runbook-lint·v1.0.3

Reads your incident-response runbook and says which of the three Article 23 clocks it gets wrong

A89/100grade A

What users say

No reviews yet

Safety scan

A89/100

Adoption

Growing

0 stars518 downloads/wk

Reviews

Nobody has reviewed Nis2 Incident Runbook Lint yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

No tool declarations could be read from the package source. They show once the server is installed.

scanner v0.1.10 · 2026-10-03 · 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.Rubric Appeal a finding JSON

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

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

From the Nis2 Incident Runbook Lint repository's README, as published. We do not edit it. Read it on GitHub

VS Code themes by ReadyStack

Nothing above is checked by us. What we check is on the safety report.

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, Cursor, VS Code or Claude Desktop 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 33 days ago (2026-10-03). The latest release is v1.0.3.
How does Nis2 Incident Runbook Lint compare with other MCP servers?: safety score 89/100 (higher than 80% of 48,243 servers); downloads a week 518 (more than 88% of 12,306 servers with a package). Full comparison.