Skip to main content
Glama
CSOAI-ORG

NIS2 Compliance MCP

enforcement_status

Check current NIS2 enforcement status and national transposition progress. Supports compliance gap analysis, readiness checks, and audit documentation.

Instructions

Current NIS2 enforcement status + national transposition tracker.

Behavior: This tool is read-only and stateless — it produces analysis output without modifying any external systems, databases, or files. Safe to call repeatedly with identical inputs (idempotent). Free tier: 10/day rate limit. Pro tier: unlimited. No authentication required for basic usage.

When to use: Use this tool when you need to assess, audit, or verify compliance requirements. Ideal for gap analysis, readiness checks, and generating compliance documentation.

When NOT to use: Do not use as a substitute for qualified legal counsel. This tool provides technical compliance guidance, not legal advice.

Args: api_key (str): The api key to analyze or process.

Behavioral Transparency: - Side Effects: This tool is read-only and produces no side effects. It does not modify any external state, databases, or files. All output is computed in-memory and returned directly to the caller. - Authentication: No authentication required for basic usage. Pro/Enterprise tiers require a valid MEOK API key passed via the MEOK_API_KEY environment variable. - Rate Limits: Free tier: 10 calls/day. Pro tier: unlimited. Rate limit headers are included in responses (X-RateLimit-Remaining, X-RateLimit-Reset). - Error Handling: Returns structured error objects with 'error' key on failure. Never raises unhandled exceptions. Invalid inputs return descriptive validation errors. - Idempotency: Fully idempotent — calling with the same inputs always produces the same output. Safe to retry on timeout or transient failure. - Data Privacy: No input data is stored, logged, or transmitted to external services. All processing happens locally within the MCP server process.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
api_keyNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The function that executes the enforcement_status tool logic. Returns JSON with NIS2 enforcement date, days since enforcement, national transposition status, key dates, and related regulations.
    def enforcement_status(api_key: str = "") -> str:
        """Current NIS2 enforcement status + national transposition tracker.
    
        Behavior:
            This tool is read-only and stateless — it produces analysis output
            without modifying any external systems, databases, or files.
            Safe to call repeatedly with identical inputs (idempotent).
            Free tier: 10/day rate limit. Pro tier: unlimited.
            No authentication required for basic usage.
    
        When to use:
            Use this tool when you need to assess, audit, or verify compliance
            requirements. Ideal for gap analysis, readiness checks, and generating
            compliance documentation.
    
        When NOT to use:
            Do not use as a substitute for qualified legal counsel. This tool
            provides technical compliance guidance, not legal advice.
    
        Args:
            api_key (str): The api key to analyze or process.
    
        Behavioral Transparency:
            - Side Effects: This tool is read-only and produces no side effects. It does not modify
              any external state, databases, or files. All output is computed in-memory and returned
              directly to the caller.
            - Authentication: No authentication required for basic usage. Pro/Enterprise tiers
              require a valid MEOK API key passed via the MEOK_API_KEY environment variable.
            - Rate Limits: Free tier: 10 calls/day. Pro tier: unlimited. Rate limit headers are
              included in responses (X-RateLimit-Remaining, X-RateLimit-Reset).
            - Error Handling: Returns structured error objects with 'error' key on failure.
              Never raises unhandled exceptions. Invalid inputs return descriptive validation errors.
            - Idempotency: Fully idempotent — calling with the same inputs always produces the
              same output. Safe to retry on timeout or transient failure.
            - Data Privacy: No input data is stored, logged, or transmitted to external services.
              All processing happens locally within the MCP server process.
        """
        now = datetime.now(timezone.utc)
        return json.dumps({
            "directive": "Directive (EU) 2022/2555 (NIS2)",
            "eu_enforcement_date": ENFORCEMENT_DATE.isoformat(),
            "days_since_eu_enforcement": (now - ENFORCEMENT_DATE).days,
            "national_transposition": "In progress across Member States — Germany (BSI-KritisV), France (ANSSI), Italy (NIS2 decreto), Netherlands (Cyberbeveiligingswet), etc.",
            "tracker_url": "https://www.enisa.europa.eu/topics/nis-directive",
            "key_dates": [
                {"date": "2023-01-16", "event": "NIS2 entered into force (EU level)"},
                {"date": "2024-10-18", "event": "Transposition deadline (Member States should have adopted national laws — many still in progress)"},
                {"date": "2025-04-17", "event": "First list of essential/important entities to be established by Member States"},
                {"date": "2027-10-17", "event": "Commission review of scope / effectiveness"},
            ],
            "related_regulations": [
                "DORA (Regulation (EU) 2022/2554) — lex specialis for financial entities",
                "Cyber Resilience Act (Regulation (EU) 2024/2847) — applies to manufacturers of products with digital elements",
                "CER Directive ((EU) 2022/2557) — physical resilience of critical entities",
            ],
        }, indent=2)
  • server.py:581-582 (registration)
    Tool registration using @mcp.tool() decorator on the enforcement_status function.
    @mcp.tool()
    def enforcement_status(api_key: str = "") -> str:
  • ENFORCEMENT_DATE constant used by the handler to compute days since enforcement.
    ENFORCEMENT_DATE = datetime(2024, 10, 18, tzinfo=timezone.utc)
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Despite no annotations, the description thoroughly discloses side effects (none), authentication requirements, rate limits, error handling, idempotency, and data privacy, exceeding basic expectations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Well-structured with clear sections, but somewhat verbose. Could be shortened without losing clarity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers all necessary aspects given the tool's simplicity: behavior, when to use, side effects, error handling, and output schema exists. Very complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds little beyond the schema for the only parameter (api_key), mentioning it in the Args section but without additional detail. With 0% schema description coverage, more guidance would be beneficial.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it provides 'Current NIS2 enforcement status + national transposition tracker' and lists specific use cases like gap analysis and readiness checks, distinguishing it from sibling tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when to use (assess, audit, verify compliance) and when NOT to use (not a substitute for legal counsel). Provides clear context for usage.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/CSOAI-ORG/nis2-compliance-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server