ISMS Copilot Docs

GDPR record of processing completeness (Article 30): free MCP tool

Call the GDPR record of processing completeness (Article 30) from your AI as a free MCP tool, no account: the inputs, a worked request and response, and how to add the server.

gdpr_ropa_completeness 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.

Scores how complete a record of processing activities is against the elements GDPR Article 30 expects, plus recommended additions such as the lawful basis: overall score and band, a score per theme, and the weakest elements to record first. A completeness aid, not a statement of GDPR compliance. Send a 0 to 4 rating for every area (0 = Not recorded, 1 = Started / ad hoc, 2 = Partially recorded, 3 = Largely recorded, 4 = Recorded & maintained); with any area missing the tool returns the open areas instead of a score. 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 GDPR record of processing completeness (Article 30) page.

Inputs

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

FieldWhat it isAllowed values
scoresOne rating per area, 0 to 4: 0 = Not recorded, 1 = Started / ad hoc, 2 = Partially recorded, 3 = Largely recorded, 4 = Recorded & maintained. Every area needs a rating before a score is computed.object (fields below)
scores.controller-identityWho is accountable: controller and contacts. Your organisation's identity and contact details as controller are recorded, along with any joint controllers and, where you are established outside the EU/EEA but caught by the GDPR, your appointed representative.whole number, 0 to 4
scores.dpo-contactData protection officer contact. Where you have appointed a DPO, their contact details are captured in the register so a supervisory authority or data subject can reach them.whole number, 0 to 4
scores.processor-mandatesControllers you act for (processor records). If you process personal data on someone else's behalf, your processor record lists your own name and contact details as processor, each controller you act for, and where applicable the processor's and each controller's representative and DPO. Skip if you only ever act as a controller. Send "not_applicable" if this does not apply to you.any
scores.purposesWhy each activity processes data. Each processing activity states the purpose it serves. As a processor, you instead record the categories of processing you carry out for each controller.whole number, 0 to 4
scores.lawful-basisLawful basis per activity. The Article 6 lawful basis for each activity (and the Article 9 condition where you handle special-category data) is noted. Article 30 does not strictly require this, but recording it makes the register far more useful and audit-ready.whole number, 0 to 4
scores.data-subjectsCategories of people whose data you process. Each activity names the categories of data subjects involved, such as customers, employees, prospects, patients, or website visitors.whole number, 0 to 4
scores.data-categoriesCategories of personal data. The categories of personal data processed in each activity are listed, such as contact details, identifiers, financial data, or location data.whole number, 0 to 4
scores.special-categoriesSpecial-category and criminal-offence data flagged. Activities involving health, biometric, racial or ethnic, political, religious, trade-union, sex-life or sexual-orientation data, or criminal-offence data, are clearly flagged, since these carry extra conditions and risk.whole number, 0 to 4
scores.recipientsCategories of recipients. Each activity records the categories of recipients the data is disclosed to, including other processors, group companies, and recipients located in third countries or international organisations.whole number, 0 to 4
scores.transfers-mappedTransfers outside the EU/EEA identified. Where personal data leaves the EU/EEA, the record identifies the third country or international organisation receiving it. Includes remote access and sub-processor hosting outside the EU/EEA, not just deliberate exports.whole number, 0 to 4
scores.transfer-safeguardsTransfer safeguards documented. For each transfer outside the EU/EEA, the Chapter V mechanism relied on (adequacy decision, standard contractual clauses, the EU-US Data Privacy Framework, or another safeguard) is recorded. Article 30 strictly requires documenting the suitable safeguards only for the narrow Article 49(1) second-subparagraph derogation transfers; recording the mechanism for every transfer is good practice and pairs with a transfer impact assessment for higher-risk routes.whole number, 0 to 4
scores.retentionRetention and erasure time limits. Each category of data has an envisaged time limit for erasure or review, rather than being kept indefinitely. Where an exact period is impossible, the criteria used to set it are recorded.whole number, 0 to 4
scores.security-measuresGeneral description of security measures. The register carries a general description of the technical and organisational measures protecting the data (Article 32(1)), such as access control, encryption, and backups, kept at a level that is meaningful but does not have to be exhaustive.whole number, 0 to 4
scores.form-and-availabilityKept in writing and available to the regulator. The record is held in writing, including electronic form, and can be produced for your supervisory authority on request. A register that cannot be exported on demand does not meet this duty.whole number, 0 to 4
scores.up-to-dateKept current as processing changes. A defined owner and cadence keep the register current, so new systems, vendors, and processing activities are added rather than the document going stale after its first version.whole number, 0 to 4
scores.scope-exemptionArticle 30(5) scope decision recorded. If you employ fewer than 250 people you have considered whether the limited Article 30(5) exemption applies, and recorded why it does not where your processing is not occasional, is likely to result in a risk to individuals, or includes special-category or criminal-offence data. Most organisations still need a record.whole number, 0 to 4

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": "gdpr_ropa_completeness",
    "arguments": {
      "scores": {
        "controller-identity": 4,
        "dpo-contact": 3,
        "processor-mandates": "not_applicable",
        "purposes": 3,
        "lawful-basis": 2,
        "data-subjects": 3,
        "data-categories": 3,
        "special-categories": 1,
        "recipients": 2,
        "transfers-mapped": 1,
        "transfer-safeguards": 0,
        "retention": 1,
        "security-measures": 2,
        "form-and-availability": 3,
        "up-to-date": 2,
        "scope-exemption": 4
      }
    }
  }
}

Response

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

{
  "status": "result",
  "overall": 2.27,
  "band": "partial",
  "band_label": "Partial",
  "groups": [
    {
      "kind": "section",
      "id": "identity",
      "label": "Accountability & contacts",
      "score": 3.5,
      "band": "well-documented"
    },
    {
      "kind": "section",
      "id": "purpose",
      "label": "Purpose & basis",
      "score": 2.5,
      "band": "mostly-complete"
    },
    {
      "kind": "section",
      "id": "data",
      "label": "Data & people",
      "score": 2.33,
      "band": "partial"
    },
    {
      "kind": "section",
      "id": "recipients",
      "label": "Recipients",
      "score": 2,
      "band": "partial"
    },
    {
      "kind": "section",
      "id": "transfers",
      "label": "International transfers",
      "score": 0.5,
      "band": "major-gaps"
    },
    {
      "kind": "section",
      "id": "retention",
      "label": "Retention",
      "score": 1,
      "band": "major-gaps"
    },
    {
      "kind": "section",
      "id": "security",
      "label": "Security measures",
      "score": 2,
      "band": "partial"
    },
    {
      "kind": "section",
      "id": "maintenance",
      "label": "Record-keeping discipline",
      "score": 3,
      "band": "mostly-complete"
    }
  ],
  "priorities": [
    {
      "id": "transfer-safeguards",
      "title": "Transfer safeguards documented",
      "group": "transfers",
      "score": 0,
      "score_label": "Not recorded"
    },
    {
      "id": "special-categories",
      "title": "Special-category and criminal-offence data flagged",
      "group": "data",
      "score": 1,
      "score_label": "Started / ad hoc"
    },
    {
      "id": "transfers-mapped",
      "title": "Transfers outside the EU/EEA identified",
      "group": "transfers",
      "score": 1,
      "score_label": "Started / ad hoc"
    },
    {
      "id": "retention",
      "title": "Retention and erasure time limits",
      "group": "retention",
      "score": 1,
      "score_label": "Started / ad hoc"
    },
    {
      "id": "lawful-basis",
      "title": "Lawful basis per activity",
      "group": "purpose",
      "score": 2,
      "score_label": "Partially recorded"
    }
  ],
  "not_applicable": [
    "processor-mandates"
  ],
  "rated": 15,
  "total": 16,
  "basis": [
    "GDPR Article 30",
    "GDPR Article 30(5)",
    "GDPR Article 32(1)"
  ],
  "sources_checked_on": [
    {
      "source": "Regulation (EU) 2016/679 (GDPR), Article 30: records of processing activities (EUR-Lex)",
      "checked_on": "2026-06-03"
    },
    {
      "source": "CNIL guidance and template for the record of processing activities",
      "checked_on": "2026-06-03"
    }
  ],
  "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-gdpr-ropa-completeness-checker",
    "label": "Review your own documents against this framework with ISMS Copilot"
  },
  "tool_page": "https://www.ismscopilot.com/resources/gdpr-ropa-completeness-checker"
}

What the result rests on

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

  • GDPR Article 30
  • GDPR Article 30(5)
  • GDPR Article 32(1)

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

  • Regulation (EU) 2016/679 (GDPR), Article 30: records of processing activities (EUR-Lex), checked 2026-06-03
  • CNIL guidance and template for the record of processing activities, checked 2026-06-03

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