CookieRisk Quickscan MCP server
eu.cookierisk/quickscancookierisk.eustreamable-httpv1.0.2Scanned
Scan a public homepage for cookies and tracking observed before consent interaction.
2 tools: 1 change things and 1 only read.
- Reads private data · 0
- Reads text others write · 1
- Can send data out · 1
- 1 finding
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 CookieRisk Quickscan MCP server can do
The CookieRisk Quickscan MCP server is published by cookierisk.eu, a domain the MCP Registry verified. It has 2 tools. It can create or change data (1 tool: start_quickscan), but cannot delete data. 1 tool only reads.
1 tool brings in text other people can write (start_quickscan); 1 tool can send data out of your system (start_quickscan).
The fixed checks matched 1 finding (credentials-mention). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 12, 2026, version 1.0.2.
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.
2 tools
Changes things 1Claude Code: ask
start_quickscanStarts a scan of a public homepage for cookies and tracking observed before consent interaction, or reuses recent evidence.Reads text others writeCan send data out1 finding
Why it is in this group
- The name "start_quickscan" says "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.
Findings
- Info
The input schema at properties.url.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.url.description: "...e https://example.com/; no path, query, credentials or fragment."
Description, as the server wrote it Starts a scan of a public homepage for cookies and tracking observed before consent interaction, or reuses recent evidence. Returns a scan ID and, for reused scans, the evidence timestamp when known and the domain cooldown end. The scan scope excludes private pages, legal verdicts, accept/reject testing, monitoring, and bulk scans. API documentation: https://cookierisk.eu/developers/mcp.
Annotations the server declares
- title: Start a CookieRisk quickscan
- readOnlyHint: false
- destructiveHint: false
- openWorldHint: true
- idempotentHint: false
Only reads 1Show 1 read-only tool
get_quickscan_resultRetrieves scan progress or sanitized findings for a CookieRisk scan ID.No findings
Why it is in this group
- The name "get_quickscan_result" says "get": a word for reading.
Description, as the server wrote it Retrieves scan progress or sanitized findings for a CookieRisk scan ID. Findings can include the visible banner provider and controls, CookieRisk score, pre-consent tracking status, tag or service classifications, browser-recorded initiator hosts, and consent signals. Page settings and scan-wide network signals are separate. A request in a tracking category alone is not confirmation. Unknown, incomplete, and failed scans do not establish absence of tracking. Accept and reject behavior is outside the scan scope.
Annotations the server declares
- title: Read a CookieRisk quickscan result
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
- idempotentHint: true
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 write1
- 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 17, 2026, 15:21 UTC, unchanged since Nov 10, 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://cookierisk.eu/mcp: tools/list returned 2 tools to an anonymous client, including start_quickscan (write)
Findings
Matches of fixed checks, with the text they matched.
- Infostart_quickscan
The input schema at properties.url.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.url.description: "...e https://example.com/; no path, query, credentials or fragment."
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools2 changed.~2 changedView diff
- Changed:get_quickscan_resultOnly readsdescriptioninputSchemaannotations
- Changed:start_quickscanChanges thingsdescriptionannotations
Install
Pinned to version 1.0.2. Values in angle brackets are yours to fill in.
claude mcp add --transport http quickscan https://cookierisk.eu/mcpclaude mcp add --transport http quickscan https://cookierisk.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__quickscan__get_quickscan_result"
],
"ask": [
"mcp__quickscan__start_quickscan"
],
"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 quickscan. Review it before you use it.
Capability tags behind 1 rule
- mcp__quickscan__start_quickscan untrusted-input, outbound
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.cookierisk/quickscan/verify?hash=1c3d6e6cd19665b7f19f7441db31f9d205233cbc5a9ca10b35428744c1e14803" | jq -e '.changed == false'Pinned hash 1c3d6e6cd196, from Nov 12, 2026, 14:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/eu.cookierisk/quickscan/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/eu.cookierisk/quickscan)Source: MCP Registry · repository. Synced Nov 12, 2026, 14:17 UTC.
CookieRisk Quickscan MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the CookieRisk Quickscan MCP server safe?
- No scan can promise that. What its definitions show: 2 tools, 1 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the CookieRisk Quickscan MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the CookieRisk Quickscan 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 CookieRisk Quickscan MCP server have?
- 2 tools: 1 write, 1 read. start_quickscan and get_quickscan_result.
Does the CookieRisk Quickscan MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the CookieRisk Quickscan 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): start_quickscan.
Has the CookieRisk Quickscan MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 12, 2026. Every change is on this page and in its Atom feed.