Nis2 Incident Runbook Lint runs on your own machine — the client starts it, so there is no endpoint to ping. 519 installs a week from npm. Last commit 22 Sep 2026.
Reads your incident-response runbook and says which of the three Article 23 clocks it gets wrong
Today is the operative word: we check Nis2 Incident Runbook Lint every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add nis2-incident-runbook-lint -- npx -y @readystack/nis2-incident-runbook-lint
{
"mcpServers": {
"nis2-incident-runbook-lint": {
"args": [
"-y",
"@readystack/nis2-incident-runbook-lint"
],
"command": "npx"
}
}
}
[mcp_servers.nis2-incident-runbook-lint]
command = "npx"
args = ["-y", "@readystack/nis2-incident-runbook-lint"]
{
"mcpServers": {
"nis2-incident-runbook-lint": {
"args": [
"-y",
"@readystack/nis2-incident-runbook-lint"
],
"command": "npx"
}
}
}
{
"mcpServers": {
"nis2-incident-runbook-lint": {
"args": [
"-y",
"@readystack/nis2-incident-runbook-lint"
],
"command": "npx"
}
}
}
Reads your stylesheet and names the success criterion each rule breaks, including the three WCAG 2.2
16 rules read your privacy.md the way Articles 13 and 14 read it
Reads the consent record your code stored and names every proof field GDPR Article 7(1) needs and yo
Reads your cloud contract text and names every clause Chapter VI no longer allows, with the article
DebugBundle MCP: runtime error reporting, incident response, health checks, and product analytics.
Search 276,000+ open source icons and insert them as SVG or React components while you code.
Twenty-two checks over the ICT vendor contracts in your repository - every missing Article 30 clause
19 offline checks on the SPF, DMARC and DKIM records in your branch — including the DMARC rewrite of
Answers built from our own checks of this server.