GDPR Privacy Monitor MCP server
eu.gdprprivacymonitor/gdpr-privacy-monitorgdprprivacymonitor.eustreamable-httpv1.0.1Scanned
Checks whether cookie consent on a website works: trackers before consent, banners, ignored rejects.
4 tools: 1 change things and 3 only read.
- Reads private data · 0
- Reads text others write · 2
- Can send data out · 1
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here changes things. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the GDPR Privacy Monitor MCP server can do
The GDPR Privacy Monitor MCP server is published by gdprprivacymonitor.eu, a domain the MCP Registry verified. It has 4 tools. It can create or change data (1 tool: scan_website), but cannot delete data. 3 tools only read.
2 tools bring in text other people can write (scan_website and get_scan_result); 1 tool can send data out of your system (scan_website).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 18, 2026, version 1.0.1.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
4 tools
Changes things 1Claude Code: ask
scan_websiteStarts 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 whet…Reads text others writeCan send data outNo findings
Why it is in this group
- The description's first verb is "start": a word for a change.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Description, as the server wrote it 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
Annotations the server declares
- title: Scan a website's cookie consent
- readOnlyHint: false
- destructiveHint: false
- openWorldHint: true
Only reads 3Show 3 read-only tools
explain_findingExplains 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 s…No findings
Why it is in this group
- The name "explain_finding" says "explain": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Explain a finding
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
get_fix_guideReturns steps to fix a finding type, optionally for a named consent management platform.No findings
Why it is in this group
- The name "get_fix_guide" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Get fix guide
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
get_scan_resultReturns 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 trac…Reads text others writeNo findings
Why it is in this group
- The name "get_scan_result" says "get": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "return" and "website": it reads web pages, which anyone can write.
Description, as the server wrote it 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.
Annotations the server declares
- title: Get scan result
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write2
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out1
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 19, 2026, 17:19 UTC, unchanged since Nov 19, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 1
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://gdprprivacymonitor.eu/mcp: tools/list returned 4 tools to an anonymous client, including scan_website (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http gdpr-privacy-monitor https://gdprprivacymonitor.eu/mcpclaude mcp add --transport http gdpr-privacy-monitor https://gdprprivacymonitor.eu/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__gdpr-privacy-monitor__get_scan_result",
"mcp__gdpr-privacy-monitor__explain_finding",
"mcp__gdpr-privacy-monitor__get_fix_guide"
],
"ask": [
"mcp__gdpr-privacy-monitor__scan_website"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as gdpr-privacy-monitor. Review it before you use it.
Capability tags behind 2 rules
- mcp__gdpr-privacy-monitor__scan_website untrusted-input, outbound
- mcp__gdpr-privacy-monitor__get_scan_result untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/eu.gdprprivacymonitor/gdpr-privacy-monitor/verify?hash=d09de9a70e0139066b5731135e8a8c127db0222b4ece4ee83e3e9b68bc38b4bb" | jq -e '.changed == false'Pinned hash d09de9a70e01, from Nov 18, 2026, 17:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/eu.gdprprivacymonitor/gdpr-privacy-monitor/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/eu.gdprprivacymonitor/gdpr-privacy-monitor)Source: MCP Registry. Synced Nov 18, 2026, 17:17 UTC.
GDPR Privacy Monitor MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the GDPR Privacy Monitor MCP server safe?
- No scan can promise that. What its definitions show: 4 tools, 1 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the GDPR Privacy Monitor MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the GDPR Privacy Monitor MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the GDPR Privacy Monitor MCP server have?
- 4 tools: 1 write, 3 read. scan_website, get_scan_result, explain_finding and get_fix_guide.
Does the GDPR Privacy Monitor MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the GDPR Privacy Monitor MCP server send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): scan_website.
Has the GDPR Privacy Monitor MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 18, 2026.