Deprecated. Deprecated by the publisher: Not affiliated with ReadyStack (readystack.dev). No new versions are published here.
Try instead
MCP server: One MCP server.Korean Law MCP3% chance this is malicious. Assessed by AI, which can make mistakes.Only reads or looks up information. Assessed by AI, which can make mistakes.External: Runs on its publisher’s own infrastructure; Odel lists it.Free to use.MCP server: One MCP server.AttestixRun by its publisher: served from their own domain, namespace checked by the registry.7% chance this is malicious. Assessed by AI, which can make mistakes.Creates or changes data. Assessed by AI, which can make mistakes.External: Runs on its publisher’s own infrastructure; Odel lists it.Free to use.MCP server: One MCP server.Shellward6% chance this is malicious. Assessed by AI, which can make mistakes.Can move money, run code, delete data or send messages for you. Assessed by AI, which can make mistakes.External: Runs on its publisher’s own infrastructure; Odel lists it.Free to use.
MCP server: One MCP server.MCP server: One MCP server.
Nis2 Incident Runbook Lint
@jmshinhwaMCP server · External
Reads your incident-response runbook and says which of the three Article 23 clocks it gets wrong
Freeno charge per call
Runs on your machine from its package; the steps are below.
What it does
- Reads
- Writes
- High impact
At most: only reads or looks up information.
What it costs
FreeOdel charges nothing per call. The publisher may charge for its own service.
Runs locally over stdio
This server isn't hosted — your MCP client launches it from a package registry. Use one of the commands below, or drop the config into your client (e.g. Claude Desktop).
npm@readystack/nis2-incident-runbook-lintv1.0.3
Run
npx -y @readystack/nis2-incident-runbook-lint
MCP client config
{
"mcpServers": {
"nis2-incident-runbook-lint": {
"command": "npx",
"args": [
"-y",
"@readystack/nis2-incident-runbook-lint"
]
}
}
}
