GDPR EU representative checker: free MCP tool
Call the GDPR EU representative checker from your AI as a free MCP tool, no account: the inputs, a worked request and response, and how to add the server.
gdpr_eu_representative 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 an organisation established outside the EU likely needs to designate an EU representative under GDPR Article 27, or may fall within the Article 27(2)(a) exemption, 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 GDPR EU representative checker page.
Inputs
The tool's input schema, as tools/list returns it, field by field.
| Field | What it is | Allowed values |
|---|---|---|
answers | One answer per question, keyed by question id. Every question needs an answer before a verdict is computed. | object (fields below) |
answers.establishedInEu | Is your organisation established in the EU/EEA, through a branch, office, or subsidiary that carries out real and effective activity? An establishment is a stable arrangement, not just a server, a mailbox address, or a single employee with no settled presence. If you have a genuine establishment in the EU/EEA, Article 3(1) applies and the Article 27 representative obligation does not arise. | yes (Yes), no (No) |
answers.dataSubjectsInUnion | Do you process the personal data of people who are in the EU/EEA? What matters is that the people are physically in the Union when the goods or services are offered or the monitoring happens, not their nationality or residence. Processing data only about people outside the Union does not engage Article 3(2). | yes (Yes), no (No) |
answers.offeringGoodsServices | Do you offer goods or services to people in the EU/EEA, whether or not payment is required? Look for an apparent intention to target people in the Union: a Union language or currency, EU country shipping or targeting, EU-based customers mentioned, an EU top-level domain. Merely being accessible from the EU is not enough on its own (Article 3(2)(a)). | yes (Yes), no (No) |
answers.monitoringBehaviour | Do you monitor the behaviour of people as far as that behaviour takes place in the EU/EEA? Examples: tracking or profiling across websites or apps, behavioural advertising, location tracking, or analytics used to take decisions about people. The behaviour being monitored must occur within the Union (Article 3(2)(b)). | yes (Yes), no (No) |
answers.publicAuthority | Is your organisation a public authority or body? Public authorities and bodies are exempt from the representative obligation under Article 27(2)(b). This is about the public-sector nature of the body, not about doing work for the public. | yes (Yes), no (No) |
answers.occasional | Is your processing of the data of people in the EU/EEA occasional, rather than regular or ongoing? Occasional means not carried out regularly and happening outside the routine course of business. The EDPB reads this narrowly: processing that is a core or repeated part of your activity is not occasional, even if it touches relatively few people. | yes (Yes), no (No) |
answers.largeScaleSpecialOrCriminal | Does your processing include, on a large scale, special-category data (Article 9) or criminal-offence data (Article 10)? Special-category data is health, biometric, genetic, racial or ethnic, religious, political, trade-union, or sex-life data. Criminal-offence data is Article 10 data. Large scale weighs the number of people, the volume and range of data, the duration, and the geographic extent. | yes (Yes), no (No) |
answers.likelyRisk | Is your processing likely to result in a risk to the rights and freedoms of the people whose data you process? Consider the nature, scope, context, and purposes of the processing. Profiling, tracking, sensitive data, decisions affecting people, and processing of vulnerable groups all point towards a risk. This is the same risk concept used across the GDPR. | yes (Yes), no (No) |
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_eu_representative",
"arguments": {
"answers": {
"establishedInEu": "no",
"dataSubjectsInUnion": "yes",
"offeringGoodsServices": "yes",
"monitoringBehaviour": "no",
"publicAuthority": "no",
"occasional": "no",
"largeScaleSpecialOrCriminal": "no",
"likelyRisk": "no"
}
}
}
}Response
The structuredContent of the result. The result's text content says the same in plain words, with the disclaimer.
{
"status": "result",
"verdict": {
"id": "required",
"reading": "Reading from fixed rules, not a legal conclusion: You likely need to designate an EU representative",
"page_title": "You likely need to designate an EU representative",
"summary": "You appear to be a controller or processor without an EU/EEA establishment whose processing falls within Article 3(2): you offer goods or services to, or monitor the behaviour of, people in the Union. Neither the public-authority exemption nor the narrow Article 27(2)(a) exemption appears to apply, so Article 27(1) requires you to designate a representative in the Union in writing. Do it before, or as you begin, the in-scope processing. If you are a controller, also identify the representative in your privacy notice.",
"tone": "in"
},
"reasons": [
{
"code": "offering-goods-services",
"text": "Trigger met: you offer goods or services to people in the Union (Article 3(2)(a))."
},
{
"code": "not-occasional",
"text": "Your processing of the data of people in the EU/EEA is regular or ongoing rather than occasional, so the Article 27(2)(a) exemption does not apply."
},
{
"code": "designate-representative",
"text": "Designate a representative in the Union in writing (Article 27(1)), established in a Member State where the data subjects whose data you process are located (Article 27(3))."
},
{
"code": "other-gdpr-obligations",
"text": "Whether or not you need a representative, your other GDPR obligations are unchanged: a lawful basis, transparency to data subjects (Articles 13 and 14), records of processing (Article 30), security (Article 32), and, where relevant, a DPIA (Article 35) and a Chapter V transfer mechanism."
}
],
"obligations": [
"Designate the representative in writing (Article 27(1)). A mandate or contract that sets out the role is the usual form.",
"Establish the representative in a Member State where the data subjects whose data you process are located (Article 27(3)).",
"Mandate the representative to be addressed, in addition to or instead of you, by supervisory authorities and data subjects on all issues related to the processing (Article 27(4)).",
"If you are a controller, identify the representative and its contact details in your privacy notice (Articles 13(1)(a) and 14(1)(a)) so data subjects and authorities can reach it. (These transparency duties fall on controllers, not processors.)",
"Keep your record of processing activities (Article 30) available, since the representative must be able to make it available to a supervisory authority on request.",
"Note that designating a representative does not affect your own responsibility or liability as controller or processor (Article 27(5)); the representative is an additional contact point, not a substitute for your duties."
],
"answered": 8,
"total": 8,
"basis": [
"GDPR Article 27",
"GDPR Article 3(2)",
"EDPB Guidelines 3/2018"
],
"sources_checked_on": [
{
"source": "Regulation (EU) 2016/679 (GDPR), Articles 27 and 3 (EUR-Lex)",
"checked_on": "2026-06-05"
},
{
"source": "EDPB Guidelines 3/2018 on the territorial scope of the GDPR (Article 3), final version 2.1, adopted 12 November 2019",
"checked_on": "2026-06-05"
}
],
"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-eu-representative-checker",
"label": "Review your own documents against this framework with ISMS Copilot"
},
"tool_page": "https://www.ismscopilot.com/resources/gdpr-eu-representative-checker"
}What the result rests on
Every result names its basis, as identifiers only (never standard text):
- GDPR Article 27
- GDPR Article 3(2)
- EDPB Guidelines 3/2018
Sources the rules were checked against, with the date each was last checked:
- Regulation (EU) 2016/679 (GDPR), Articles 27 and 3 (EUR-Lex), checked 2026-06-05
- EDPB Guidelines 3/2018 on the territorial scope of the GDPR (Article 3), final version 2.1, adopted 12 November 2019, checked 2026-06-05
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.