ISMS Copilot Docs

Cyber Resilience Act applicability checker: free MCP tool

Call the Cyber Resilience Act applicability checker from your AI as a free MCP tool, no account: the inputs, a worked request and response, and how to add the server.

cra_applicability is one of the 20 free GRC tools from ISMS Copilot that any AI client can call over MCP: no account, no model, one call.

Reads whether a product is likely in scope of the Cyber Resilience Act (Regulation (EU) 2024/2847) and, if so, in which class (default, important Class I or II, critical), or likely out of scope or excluded, with the reasons. Answer every question (the input schema lists them with their options); with any question unanswered the tool returns the open questions instead of a verdict. The verdict is a reading from fixed rules, not a legal conclusion. Returns general information from a fixed rule set; confirm against the official text.

This page is about calling the tool from an AI client: the request, the response and the setup. For the same tool on the web, with the background on the rules it applies, open the Cyber Resilience Act applicability checker page.

Inputs

The tool's input schema, as tools/list returns it, field by field.

FieldWhat it isAllowed values
answersOne answer per question, keyed by question id. Every question needs an answer before a verdict is computed.object (fields below)
answers.euMarketIs the product made available on the EU market in the course of a commercial activity? The CRA applies to products with digital elements placed on the EU market; free and open-source software supplied outside a commercial activity is treated separately (see the exclusions step).yes (Yes), no (No)
answers.kindWhat are you assessing? A product with digital elements is hardware or software whose intended or reasonably foreseeable use includes a direct or indirect data connection to a device or network.pde (A product with digital elements (hardware or software that connects)), remote-data-processing (A remote data-processing solution that is integral to such a product), not-pde (A standalone service / something with no digital elements (not a product))
answers.exclusionDoes any of these scope exclusions apply? These take the product outside the CRA, most are Article 2 carve-outs (typically sector-specific law); free/open-source software supplied outside a commercial activity is outside scope on a different basis (it is not 'placed on the market').sector-law (Already covered by sector law, medical devices, motor vehicles, civil aviation, or marine equipment), national-security-defence (Developed or modified exclusively for national security or defence), classified-info (Designed exclusively to process classified information), spare-parts (A spare part replacing an identical component, with the same specifications), noncommercial-oss (Free and open-source software supplied outside a commercial activity), none (None of these apply)
answers.productClassWhich CRA product class best fits? Class is set by the Annex III/IV categories and the Commission technical descriptions, pick the closest match.critical (Critical (Annex IV), e.g. hardware with security boxes, smart-meter gateways, smartcards / secure elements), important-ii (Important, Class II (Annex III), e.g. firewalls, intrusion detection/prevention, hypervisors, tamper-resistant microprocessors), important-i (Important, Class I (Annex III), e.g. password managers, VPNs, network management, SIEM, browsers, security-relevant smart-home/IoT), default (None of those, a product with digital elements not in Annex III or IV)

If an answer is missing

The tool never guesses an answer. A call with any field left out returns status: "needs_answers" and the open questions, each with its id, its text and its allowed values, and no result. Your AI can ask you those questions and call again.

Worked example

This request and response come from the tool itself: the catalog runs the tool's handler on this example input, and this page is generated from that catalog.

Request

A tools/call request, as your client sends it:

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "cra_applicability",
    "arguments": {
      "answers": {
        "euMarket": "yes",
        "kind": "pde",
        "exclusion": "none",
        "productClass": "important-i"
      }
    }
  }
}

Response

The structuredContent of the result. The result's text content says the same in plain words, with the disclaimer.

{
  "status": "result",
  "verdict": {
    "id": "in-scope-important-i",
    "reading": "Reading from fixed rules, not a legal conclusion: In scope: important product, Class I (Annex III)",
    "page_title": "In scope: important product, Class I (Annex III)",
    "summary": "On your answers this is an important product, Class I. Conformity can be self-assessed if harmonised standards / a certification scheme are applied in full; otherwise a third-party assessment is required.",
    "tone": "in"
  },
  "reasons": [
    {
      "code": "annex-iii-class-i",
      "text": "An important product, Annex III Class I."
    }
  ],
  "obligations": [
    "Essential cybersecurity requirements (Annex I), secure-by-design and -default, vulnerability handling across the support period.",
    "Conformity assessment + CE marking, self-assessment for default products; third-party for important Class II and most critical products.",
    "Technical documentation, EU declaration of conformity, and clear security-relevant user information.",
    "Vulnerability and severe-incident reporting to ENISA/CSIRT (Art. 14), applies from 11 September 2026.",
    "Obligations also depend on your role, manufacturer (primary), importer or distributor, which this tool does not determine."
  ],
  "answered": 4,
  "total": 4,
  "basis": [
    "Regulation (EU) 2024/2847 Articles 2 and 3",
    "Regulation (EU) 2024/2847 Annexes III and IV"
  ],
  "sources_checked_on": [
    {
      "source": "Regulation (EU) 2024/2847 (Cyber Resilience Act), EUR-Lex",
      "checked_on": "2026-07-17"
    },
    {
      "source": "European Commission: Cyber Resilience Act policy page",
      "checked_on": "2026-07-17"
    }
  ],
  "disclaimer": "General information from a fixed rule set, not legal advice. Check the result against the official text and with a qualified professional before you act on it.",
  "more": {
    "url": "https://www.ismscopilot.com/mcp?ref=mcp-tool-cra-applicability-checker",
    "label": "Review your own documents against this framework with ISMS Copilot"
  },
  "tool_page": "https://www.ismscopilot.com/resources/cra-applicability-checker"
}

What the result rests on

Every result names its basis, as identifiers only (never standard text):

  • Regulation (EU) 2024/2847 Articles 2 and 3
  • Regulation (EU) 2024/2847 Annexes III and IV

Sources the rules were checked against, with the date each was last checked:

  • Regulation (EU) 2024/2847 (Cyber Resilience Act), EUR-Lex, checked 2026-07-17
  • European Commission: Cyber Resilience Act policy page, checked 2026-07-17

Add the server

claude mcp add --scope user --transport http ismscopilot-free-tools 'https://www.ismscopilot.com/api/public/tools/mcp'

That is Claude Code. For claude.ai, Claude Desktop, ChatGPT, Cursor, Codex and any other client, see Add the server to your client. No sign-in, no token.

Limits

General information from a fixed rule set, not legal advice. Check the result against the official text and with a qualified professional before you act on it.

Your inputs are never logged or stored by our code. We count calls per tool (the tool name, whether it produced a result and when, nothing else). Our host keeps standard request logs (time, path, status, client address) for a short period. Do not send personal data: no tool needs any.

A fixed rule cannot read your own policies, registers or contracts. For a review of your own documents, connect ISMS Copilot, the GRC expert your AI calls.

On this page