GDPR Privacy Monitor
Remote MCP server that scans a website's cookie consent from your AI assistant
Answered our latest tool-list check 5 hours ago with 4 tools. It will be marked verified after 3 successful checks in 7 days.
- Platforms
- API, Web
- Runs
- Remotely
- Version
- 1.0.1
- Listing updated
- today
Similar MCP servers
About GDPR Privacy Monitor
GDPR Privacy Monitor is an MCP server for compliance and regulation. It runs as a hosted remote server, so there is nothing to install locally.
The MCP server lets an AI assistant trigger a real-browser scan of a public website and report on its cookie consent setup. The scan checks whether trackers load before the visitor consents, whether a consent banner appears, and whether a rejection is actually honoured. Results include a risk score, the cookies and trackers seen before consent, and the most important findings, with a link to the full report on the website.
Beyond scanning, the assistant can explain individual findings in plain language in any of 24 supported languages, and show fix steps for popular consent platforms such as Cookiebot, CookieYes, OneTrust, Complianz and iubenda. The server is reached over streamable HTTP and needs no account or authentication.
It suits site owners, agencies and privacy staff who want a quick consent check inside Claude or ChatGPT rather than a separate dashboard. The provider notes that new scans through assistants share a daily capacity, and that a scan of the same address is reused for 24 hours.
Install
Run in a terminal
claude mcp add --transport http gdpr-privacy-monitor https://gdprprivacymonitor.eu/mcpAdd to Settings → Connectors → Add custom connector
https://gdprprivacymonitor.eu/mcpAdd to ~/.cursor/mcp.json
{
"mcpServers": {
"gdpr-privacy-monitor": {
"url": "https://gdprprivacymonitor.eu/mcp"
}
}
}Add to .vscode/mcp.json
{
"servers": {
"gdpr-privacy-monitor": {
"type": "http",
"url": "https://gdprprivacymonitor.eu/mcp"
}
}
}Add to ~/.codeium/windsurf/mcp_config.json
{
"mcpServers": {
"gdpr-privacy-monitor": {
"serverUrl": "https://gdprprivacymonitor.eu/mcp"
}
}
}Add to Grok Bot desktop app → Connect apps → Add a custom connector
https://gdprprivacymonitor.eu/mcpEnter a Name (for example "GDPR Privacy Monitor"), choose Type: Remote HTTPS, paste this as the Server URL and choose Add plugin.
Add to your client's MCP settings (most use this shape)
{
"mcpServers": {
"gdpr-privacy-monitor": {
"type": "http",
"url": "https://gdprprivacymonitor.eu/mcp"
}
}
}Using several servers? Build one config file with the MCP config generator.
Tools this server provides (4)
Read directly from the server.
3 of 4 tools say they're read-only. 1 of 4 tools says it can delete or change data.
From the server's own tool annotations; not verified by us.
- scan_websiteSays it can change data
- 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 i
- get_scan_resultSays read-only
- 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 q
- explain_findingSays read-only
- 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.
- get_fix_guideSays read-only
- 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.
What it does
- Real-browser consent scan
- Runs a browser-based scan of a public site to see what loads before consent and how the banner behaves.
- Rejection flow check
- Tests whether declining cookies is actually respected by the site's trackers.
- Plain-language finding explanations
- Explains individual findings in any of 24 languages.
- Platform-specific fix guides
- Gives fix steps tailored to Cookiebot, CookieYes, OneTrust, Complianz and iubenda.
- Cached scan results
- Returns a recent scan of the same address for 24 hours instead of rescanning.
Good for
- Checking whether a website loads trackers before visitors accept cookies
- Verifying that a cookie reject button really stops tracking on a shop site
- Understanding a specific consent finding and how to fix it in a given CMP
- Running a quick consent check from inside Claude or ChatGPT
GDPR Privacy Monitor FAQ
Does the server require an account or API key?
The provider states that no account or sign-in is needed, and the registry entry lists no authentication.
Which transport does it use?
It uses Streamable HTTP at the server URL https://gdprprivacymonitor.eu/mcp.
Is there a daily limit?
New scans requested through AI assistants share a daily capacity; when it runs out, the assistant links to the scan form on the website.
What happens to the data sent to the server?
The provider says the server receives only the website address and requested language, not the conversation. Scans are deleted after 7 days and no account or IP address is stored with them.
How do I add GDPR Privacy Monitor to Claude Code?
Run this command in your terminal: claude mcp add --transport http gdpr-privacy-monitor https://gdprprivacymonitor.eu/mcp
Where this comes from
- Description: written from the project's website and its MCP Registry entry.
- Status and tools: checked automatically by AIPoweredBot on 19 November 2026.
- Install steps: from the official MCP Registry entry.