MCP servers · csoai-org

NIS2 Compliance MCP

MCP server for checking compliance with the NIS2 Directive (EU 2022/2555), covering entity classification, an audit of the ten Article 21 risk-management measures and incident reporting.

This text was machine-translated from the publisher's own information and has not been checked by a human editor. The publisher's original text is the reference.

This resource was imported automatically from the sources listed below and has not been reviewed by the AI Gate team yet. The description is the publisher's own, as published. Check the repository before installing.

What it does

The server covers Articles 21 and 23 of the NIS2 Directive. It offers tools to classify an entity, list the ten Article 21 risk-management measures, audit an entity against them and support incident reporting. Each tool is called from an MCP-compatible assistant, for example by asking it to use classify_entity, list_article_21_measures or audit_article_21.

It suits teams that need to check NIS2 obligations from inside an AI assistant or agent workflow, rather than by reading the directive by hand. The MIT-licensed package is published on PyPI.

To run it, install the nis2-compliance-mcp package with pip and start the nis2-compliance-mcp command, which uses the stdio transport. Alternatively, add the server to the configuration file of your MCP client, such as claude_desktop_config.json for Claude Desktop. The publisher's README describes a free tier of 50 calls per day and a pay-per-call option that is enabled through the MEOK_PAYG_KEY variable.

Limitations and requirements

The free tier is limited to 50 calls per day. Beyond that, usage depends on pay-per-call billing, which requires a token from councilof.ai and a prepaid top-up. The per-call rate is set through MEOK_PAYG_RATE_GBP, and stablecoin payment on Base L2 requires MEOK_X402_RECEIVER to be set.

Safety

Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.

  • Runs code or changes an assistant's behaviour

Sources

  • Official MCP Registry first seen 13 Nov 2026 · last seen 13 Nov 2026 · its page on the source
    io.github.CSOAI-ORG/nis2-compliance-mcp

    NIS2 Directive (EU 2022/2555) compliance for AI agents. 10 Article 21 risk-management measures a...

    v1.3.11
    As shown on registry.modelcontextprotocol.io when we last read it
MCP servers
modelcontextprotocol

MCP reference servers

Seven small example servers maintained by the Model Context Protocol project: files, Git, web fetching, memory, time, step-by-step thinking and a test server.

92K GitHub starsSoftware development
Updated 18 Nov 2026
MCP servers
firecrawl

Firecrawl MCP Server (web search and scraping)

Firecrawl's MCP server that lets an AI assistant search the web, turn pages and PDFs into clean Markdown, crawl sites and interact with dynamic pages.

7.8K GitHub starsWeb, search & browserProductivity & automation
Updated 17 Nov 2026
MCP servers
hashicorp

Terraform MCP Server (HashiCorp)

HashiCorp's MCP server that gives an assistant current Terraform Registry information on providers, modules and policies, and can manage HCP Terraform workspaces.

1.6K GitHub starsCloud & DevOpsSoftware development
Updated 17 Nov 2026
MCP servers
docker

Docker Hub MCP Server

Docker's MCP server that helps an AI assistant find and compare container images on Docker Hub and, with your token, manage your own repositories and tags.

171 GitHub starsCloud & DevOpsSoftware development
Updated 13 Nov 2026