Skip to main content
Glama

Server Details

Checks whether cookie consent on a website works: trackers before consent, banners, ignored rejects.

If you are the author of this connector, you can claim ownership. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
ChatGPT
–
Claude
GDPR Privacy Monitor

TDQS

A4.1/5.0

Scored across 4 tools

Disambiguation5/5

Each tool occupies a distinct slot in a linear workflow: scan_website starts a scan, get_scan_result reads its outcome, explain_finding explains a finding type, and get_fix_guide gives remediation steps. The only pair that could be confused (explain_finding vs get_fix_guide) is explicitly separated as 'what/why it matters' versus 'steps to fix', including platform-specific steps in the latter. No two tools appear to do the same thing.

Naming Consistency5/5

All four names are snake_case verb_noun (scan_website, get_scan_result, explain_finding, get_fix_guide), with the resource or object always last. The verbs are meaningful and consistent in style, with no mixing of camelCase or noun-only names.

Tool Count4/5

Four tools is a tight but coherent surface for a single-purpose scan-and-report server, and each tool clearly earns its place. It sits at the low end of the comfortable range, leaving no room for ancillary operations such as listing or cancelling prior scans.

Completeness4/5

The core lifecycle is covered end to end: initiate a scan (with 24h dedupe and capacity-limit messaging), poll status/results, understand a finding, and remediate it. Minor gaps remain, such as no way to list, cancel, or re-read past scans through the server, but agents can work around these via the returned report links.

Available Tools

4 tools
explain_findingExplain a findingA
Read-only
Inspect

Explains a GDPR Privacy Monitor finding type, such as pre_consent_tracker or reject_flow_failed: what was detected, why it matters, and suggested wording for explaining it to the site owner, in the requested language. Looks the type up in a fixed catalogue; it does not scan anything. Technical explanation, not legal advice.

Inputs: finding_type (required), language.

get_fix_guideGet fix guideA
Read-only
Inspect

Returns steps to fix a finding type, optionally for a named consent management platform. Cookiebot, CookieYes, OneTrust, Complianz and iubenda have platform-specific steps (in English); for other platforms, or without one, the general steps apply. Includes links to the matching fix guide and knowledge articles on gdprprivacymonitor.eu. Read-only lookup.

Inputs: finding_type (required), cmp, language.

get_scan_resultGet scan resultA
Read-only
Inspect

Returns the status of a scan started with scan_website and, once it has finished, a summary: risk score and level, whether a consent banner was detected, counts of cookies and trackers before consent, and the most important findings with plain-language explanations in the requested language, plus a link to the full web report. Only scans started through this server can be read. While the scan is queued or running, call again after about 20 seconds.

Inputs: scan_id (required), language.

scan_websiteScan a website's cookie consentAInspect

Starts an automated real-browser scan of a public website to check its cookie consent behaviour: cookies and trackers set before consent, whether a consent banner appears, and whether rejecting consent is honoured. Side effect: queues a new scan on GDPR Privacy Monitor, unless the same URL was scanned through this server in the last 24 hours or is being scanned right now, in which case that scan is returned instead. Returns the scan_id, its status and a link to the web report; a scan usually finishes within one to two minutes, after which get_scan_result returns the findings. Only http(s) URLs of publicly reachable sites are accepted. New scans are subject to a daily capacity limit; when it is reached the tool returns an error with a link for running the scan on the website instead. Documentation: https://gdprprivacymonitor.eu/en/developers/mcp

Inputs: url (required), language.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      B
      maintenance
      Enables auditing one or many websites from an EU address for cookie consent behavior, returning per-domain rows on the consent platform, first-layer reject availability, trackers and tracking cookies before consent and after reject, and Global Privacy Control response. Runs the work on Apify and hands back the dataset rows through a single tool.
      1
      62 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to run EU cookie-consent audits on public websites, checking pre-consent trackers, banner rejection behavior, Consent Mode v2, IAB TCF, GPC, undisclosed cookies, and third-party embeds, with findings, evidence, fixes, and legal references.
      MIT
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources