CookieRisk MCP
An MCP server that allows AI assistants to scan a single public homepage for cookies and tracking observed before any consent banner interaction. It provides point-in-time observations of tracking categories, CMP signals, and Google Consent Mode settings without requiring user authentication or account creation.
Endpoint and access
No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.
https://cookierisk.eu/mcpWhat its tools do
2 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.
Read-only (1)
Can change data (1)
Checks and signals
Each line is separate evidence, not a trust score.
- Passed Endpoint answered the live check ·
- Passed Official MCP Registry namespace is tied to cookierisk.eu ·
- Passed Endpoint is on the registry namespace domain ·
- Availability 1 of 1 checks passed in 30 days
What you can do with it
- Scan a public homepage for cookies and tracking observed before consent interaction
- Check for banner provider and controls visible on the first layer
- Retrieve CookieRisk score and limitations for a specific domain
Source and maintenance
Protocol and capabilities
- Server
- cookierisk-quickscan 1.0.0
- MCP protocol negotiated in check
- 2025-11-25
- Tools
- 2 advertised
- Resources
- Not advertised
- Resource templates
- Not advertised
- Prompts
- Not advertised
{
"tools": {
"listChanged": true
}
}Tools
2 advertised
start_quickscan — Start a CookieRisk quickscan
Use this when a user asks to check a public website homepage for cookies and tracking observed before interaction. Creates a scan and visits the website. Only submit the homepage URL; do not use for private pages, legal verdicts, accept/reject testing, monitoring, or bulk scans. If reused is true, tell the user right away when the evidence was recorded (evidenceCapturedAt, if known) and when the domain cooldown ends (domainCooldownEndsAt). A new scan still depends on capacity. Poll get_quickscan_result using the returned scanId and wait pollAfterSeconds between reads.
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"url"
],
"properties": {
"url": {
"type": "string",
"maxLength": 2048,
"minLength": 1,
"description": "Public HTTP(S) homepage, for example https://example.com/; no path, query, credentials or fragment."
}
},
"additionalProperties": false
}{
"readOnlyHint": false,
"openWorldHint": true,
"idempotentHint": false,
"destructiveHint": false
}get_quickscan_result — Read a CookieRisk quickscan result
Use the scanId returned by start_quickscan to retrieve progress or sanitized findings, including the visible banner provider and controls, CookieRisk score, pre-consent tracking status, tag or service classifications, browser-recorded initiator hosts and consent signals when available. Page settings and scan-wide network signals are separate. A request in a tracking category alone is not confirmation. Observe pollAfterSeconds before polling and retryAfter on an error. Unknown, incomplete and failed scans do not establish absence of tracking. Accept and reject behavior is outside the scan scope.
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"scanId"
],
"properties": {
"scanId": {
"type": "string",
"format": "uuid",
"pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
"description": "The scanId returned by start_quickscan."
}
},
"additionalProperties": false
}{
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}Prompts
Not advertised
Resources
Not advertised
90-day uptime
A lightweight connection check about every six hours, sampled on hosts with many listings. It shows the server answered, not that its tools work.
- 2026-11-09: 1 of 1 checks answered
30-day availability
Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.
- Successful checks
- 1 of 1 (100%)
- Average latency
- 886 ms
- 95th percentile latency
- 886 ms
Maintenance history
Public check and source-refresh events. Editorial and ownership records remain private.
- · probe · passed · 886 ms · metadata changed · 2 tool(s)
Connect from your client
Each snippet registers the same endpoint; pick the client you use.
Claude Code
claude mcp add --transport http cookierisk-mcp https://cookierisk.eu/mcpCodex
codex mcp add cookierisk-mcp --url https://cookierisk.eu/mcpCursor
{
"mcpServers": {
"cookierisk-mcp": {
"url": "https://cookierisk.eu/mcp"
}
}
}Cline
{
"mcpServers": {
"cookierisk-mcp": {
"type": "streamableHttp",
"url": "https://cookierisk.eu/mcp",
"disabled": false
}
}
}VS Code
{
"servers": {
"cookierisk-mcp": {
"type": "http",
"url": "https://cookierisk.eu/mcp"
}
}
}Gemini CLI
gemini mcp add --transport http cookierisk-mcp https://cookierisk.eu/mcpClaude Desktop
https://cookierisk.eu/mcpWindsurf
{
"mcpServers": {
"cookierisk-mcp": {
"serverUrl": "https://cookierisk.eu/mcp"
}
}
}Let your agent find its tools
Find servers like CookieRisk MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.
Other ai and machine learning servers
Do you run CookieRisk MCP?
Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.