ISMS Copilot Docs

Cookie consent checker (ePrivacy and GDPR): free MCP tool

Call the Cookie consent checker (ePrivacy and GDPR) from your AI as a free MCP tool, no account: the inputs, a worked request and response, and how to add the server.

gdpr_cookie_consent 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 the cookies and trackers on a site likely need prior consent under Article 5(3) of the ePrivacy Directive, and whether the consent collected likely meets the GDPR standard, 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 Cookie consent checker (ePrivacy and GDPR) 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.storesOrAccessesDoes your website or app store information on, or read information already stored on, a user's device? Article 5(3) of the ePrivacy Directive is about storing or accessing information on the user's terminal equipment, whatever the technology: cookies, local storage, an SDK, a tracking pixel, or device fingerprinting all count. If you place or read nothing on the device at all, the cookie rule does not engage.yes (Yes), no (No)
answers.cookieTypesWhich best describes what you store or read on the user's device? This is the decisive question. The cookie rule exempts only what is strictly necessary to deliver a service the user explicitly asked for (for example a session cookie that keeps them logged in, a load-balancing cookie, a shopping-cart cookie, or a cookie that remembers a cookie-consent choice). Anything beyond that, including analytics and advertising, generally needs consent. Pick the highest category that applies to you.strictly-necessary-only (Only strictly necessary items, needed to deliver a service the user explicitly requested (session, security, load-balancing, basic cart, remembering the consent choice).), includes-analytics (Also analytics, measurement, or A/B-testing cookies or trackers (for example to count visitors or study how the site is used).), includes-marketing (Also advertising, retargeting, social-media, or other third-party tracking cookies or trackers.), unsure (I am not sure which categories of cookies and trackers are in use.)
answers.consentBeforePlacingDo your non-essential cookies and trackers fire only after the user gives consent, rather than on page load? Consent under Article 5(3) must be prior: non-essential cookies and trackers may be set only once the user has agreed. Loading analytics or advertising scripts on the first page view, before any choice is made, means they ran without consent. Strictly necessary items may still load without consent. If you use no non-essential cookies, this does not change the result.yes (Yes), no (No)
answers.affirmativeActionIs consent collected by a clear affirmative action, with no pre-ticked boxes and no consent inferred from silence or scrolling? GDPR consent must be unambiguous and given by a clear affirmative act (Article 4(11)). A pre-ticked box, a banner that only offers "OK", "by continuing to browse you accept", or consent assumed from scrolling are not valid consent. The CJEU confirmed this for cookies in Planet49 (Case C-673/17). If you use no non-essential cookies, this does not change the result.yes (Yes), no (No)
answers.refuseAsEasyIs refusing as easy as accepting, with a reject option as prominent and easy to use as the accept option? Consent must be freely given (Article 7). The EDPB Cookie Banner Taskforce and most national authorities read this as requiring a reject option as prominent and easy as the accept option, typically on the same layer of the banner. Separately, denying access to the service unless the user consents to non-necessary cookies (a cookie wall) can undermine free consent, though the position is contested and some authorities permit limited "consent or pay" models under conditions, so check your national guidance on cookie walls. If you use no non-essential cookies, this does not change the result.yes (Yes), no (No)
answers.easyWithdrawCan users withdraw their consent at any time, as easily as they gave it? Article 7(3) gives users the right to withdraw consent at any time, and it must be as easy to withdraw as to give. In practice that usually means a persistent way to reopen the cookie settings and change or revoke the choice. If you use no non-essential cookies, this does not change the result.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_cookie_consent",
    "arguments": {
      "answers": {
        "storesOrAccesses": "yes",
        "cookieTypes": "includes-analytics",
        "consentBeforePlacing": "no",
        "affirmativeAction": "yes",
        "refuseAsEasy": "no",
        "easyWithdraw": "yes"
      }
    }
  }
}

Response

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

{
  "status": "result",
  "verdict": {
    "id": "consent-required",
    "reading": "Reading from fixed rules, not a legal conclusion: You need prior consent before these cookies or trackers run",
    "page_title": "You need prior consent before these cookies or trackers run",
    "summary": "On your answers you store or read non-essential cookies or trackers on the user's device, so Article 5(3) of the ePrivacy Directive requires the user's prior consent, given to the GDPR standard, before they fire. That means clear and comprehensive information up front, non-essential scripts held back until the user agrees, a genuine choice to accept or refuse, and an easy way to withdraw. The requirements are summarised below, and any gaps your answers pointed to are listed under \"Why this result\". Strictly necessary items may still run without consent.",
    "tone": "in"
  },
  "reasons": [
    {
      "code": "non-essential-consent-required",
      "text": "You indicated you use cookies or trackers beyond the strictly necessary, so under Article 5(3) you need the user's prior consent before they are set or read. Non-essential scripts must be held back until the user has agreed."
    },
    {
      "code": "consent-standard-gdpr",
      "text": "The consent the ePrivacy Directive requires is consent to the GDPR standard: freely given, specific, informed, and unambiguous, given by a clear affirmative action (Article 4(11)), and as easy to withdraw as to give (Article 7(3))."
    },
    {
      "code": "analytics-not-strictly-necessary",
      "text": "Analytics and measurement cookies are generally not strictly necessary and so need consent. A few national authorities allow a narrow exemption for privacy-preserving audience measurement under strict conditions, so check your national authority's guidance before relying on one."
    },
    {
      "code": "placed-before-consent-gap",
      "text": "You indicated non-essential cookies or trackers fire on page load rather than after consent. Consent under Article 5(3) must be prior: hold non-essential scripts and tags until the user has actively agreed, and let strictly necessary items load in the meantime."
    },
    {
      "code": "refuse-as-easy-gap",
      "text": "You indicated refusing is not as easy as accepting. For consent to be freely given (Article 7), the EDPB Cookie Banner Taskforce and most national authorities expect a reject option as prominent and easy as accept, usually on the same layer. Separately, many authorities treat blocking the service behind consent (a cookie wall) as undermining free consent, though that is contested. Make refusing a one-step, equally visible choice and check your national guidance on cookie walls."
    },
    {
      "code": "exemption-is-narrow",
      "text": "The strictly-necessary exemption in Article 5(3) is narrow: it covers only what is essential to deliver a service the user explicitly requested, or what is solely needed to carry out a transmission. It is judged against that requested service, not against what is convenient for you, so analytics, advertising, and most third-party trackers generally fall outside it."
    }
  ],
  "obligations": [
    "Give clear and comprehensive information before consent: what you store or read, why, how long cookies last, and who the third parties are, in plain language and before any non-essential cookie is set (Article 5(3); GDPR Articles 4(11) and 13).",
    "Hold non-essential cookies and trackers until the user has actively agreed; let only strictly necessary items load beforehand (Article 5(3)).",
    "Collect consent by a clear affirmative action: no pre-ticked boxes, no accept-only banners, and no consent inferred from silence, inactivity, or scrolling (Article 4(11); CJEU Planet49, Case C-673/17).",
    "Make refusing as easy as accepting, with a reject option as prominent and easy as accept (Article 7, as read by the EDPB Cookie Banner Taskforce), and avoid conditioning access to the service on consent where that would make it not freely given (check national guidance on cookie walls).",
    "Keep consent specific and granular, so users can agree to some purposes (for example analytics) and not others (for example advertising), rather than a single all-or-nothing choice (Article 4(11)).",
    "Let users withdraw consent at any time, as easily as they gave it, for example through a persistent link that reopens the cookie settings (Article 7(3)).",
    "Record consent so you can demonstrate it: who consented, when, to what information, and to which purposes (Article 7(1)).",
    "Do not treat consent as permanent: refresh it when purposes or third parties change, and re-ask within a sensible period rather than relying on a years-old choice."
  ],
  "answered": 6,
  "total": 6,
  "basis": [
    "Directive 2002/58/EC Article 5(3)",
    "GDPR Articles 4(11) and 7",
    "EDPB Guidelines 05/2020"
  ],
  "sources_checked_on": [
    {
      "source": "Directive 2002/58/EC (ePrivacy Directive), Article 5(3), consolidated text incorporating Directive 2009/136/EC (EUR-Lex CELEX 02002L0058-20091219)",
      "checked_on": "2026-09-09"
    },
    {
      "source": "Regulation (EU) 2016/679 (GDPR), Articles 4(11), 7, and 13, for the standard of consent (EUR-Lex)",
      "checked_on": "2026-09-09"
    },
    {
      "source": "EDPB Guidelines 05/2020 on consent under Regulation 2016/679, version 1.1, adopted 4 May 2020",
      "checked_on": "2026-09-09"
    },
    {
      "source": "EDPB Report of the work undertaken by the Cookie Banner Taskforce, adopted 18 January 2023 (on reject controls and banner design)",
      "checked_on": "2026-09-09"
    },
    {
      "source": "CJEU, Planet49 (Case C-673/17), judgment of 1 October 2019 (pre-ticked boxes are not valid cookie consent)",
      "checked_on": "2026-09-09"
    },
    {
      "source": "EDPB Opinion 08/2024 on Valid Consent in the Context of Consent or Pay Models Implemented by Large Online Platforms, adopted 17 April 2024",
      "checked_on": "2026-09-09"
    },
    {
      "source": "CNIL, Sheet no. 16: Use analytics on your websites and applications (national worked example of a conditional audience-measurement exemption under French law, not a general EU rule)",
      "checked_on": "2026-09-09"
    }
  ],
  "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-cookie-consent-checker",
    "label": "Review your own documents against this framework with ISMS Copilot"
  },
  "tool_page": "https://www.ismscopilot.com/resources/gdpr-cookie-consent-checker"
}

What the result rests on

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

  • Directive 2002/58/EC Article 5(3)
  • GDPR Articles 4(11) and 7
  • EDPB Guidelines 05/2020

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

  • Directive 2002/58/EC (ePrivacy Directive), Article 5(3), consolidated text incorporating Directive 2009/136/EC (EUR-Lex CELEX 02002L0058-20091219), checked 2026-09-09
  • Regulation (EU) 2016/679 (GDPR), Articles 4(11), 7, and 13, for the standard of consent (EUR-Lex), checked 2026-09-09
  • EDPB Guidelines 05/2020 on consent under Regulation 2016/679, version 1.1, adopted 4 May 2020, checked 2026-09-09
  • EDPB Report of the work undertaken by the Cookie Banner Taskforce, adopted 18 January 2023 (on reject controls and banner design), checked 2026-09-09
  • CJEU, Planet49 (Case C-673/17), judgment of 1 October 2019 (pre-ticked boxes are not valid cookie consent), checked 2026-09-09
  • EDPB Opinion 08/2024 on Valid Consent in the Context of Consent or Pay Models Implemented by Large Online Platforms, adopted 17 April 2024, checked 2026-09-09
  • CNIL, Sheet no. 16: Use analytics on your websites and applications (national worked example of a conditional audience-measurement exemption under French law, not a general EU rule), checked 2026-09-09

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