CookieRisk
MCP server by CookieRisk
Scan a public website homepage for cookies and tracking that fire before consent and read the resulting findings.
Connect to CookieRisk
No sign-in needed. Connect with CookieRisk’s own URL:
Paste it into any client that supports remote MCP servers. Your client talks to CookieRisk directly, not through mcp.tc.
Share this server
Opens this page, with the URL and setup steps.
mcp.tc/i/cookieriskAbout
CookieRisk Quickscan checks a public website homepage for cookies and tracking observed before any interaction with the cookie banner. It starts a scan in a real browser and returns findings such as the visible banner provider and controls, a CookieRisk score, pre-consent tracking status, tag and service classifications, initiator hosts and consent signals.
The server runs as a hosted streamable HTTP endpoint at https://cookierisk.eu/mcp. No sign-in or API key is needed. Scans are for homepages only, and a domain cooldown and capacity limits can apply to repeat scans.
What you can do
- Start a quickscan of a public website homepage
- Poll scan progress and read sanitized findings
- See the visible cookie banner provider and controls
- Get a CookieRisk score and pre-consent tracking status
- Review tag and service classifications and initiator hosts
Tools 2
start_quickscanWritesCreate a quickscan for a public homepage URL and return a scanId and polling interval.
get_quickscan_resultRead-onlyRead progress or sanitized findings for a scan by scanId, including score and tracking status.
Read from the live server on 18 Nov 2026. Read-only, Writes and Can delete are hints the server declares; your client decides whether to ask before running a tool.
Example prompts
Run a CookieRisk quickscan on example.com and summarize the tracking found before consent.
Which cookie banner provider does example.com use, and what is its CookieRisk score?
Check whether my homepage fires trackers before the user interacts with the banner.
Get the result for scan ID abc123 and list the tracking services it classified.
Set up
Every client connects to cookierisk.eu. Pick yours; the page remembers your choice.
Claude Code
- Run this in a terminal, in your project folder:
claude mcp add --transport http cookierisk https://cookierisk.eu/mcp- Start Claude Code and type
/mcp. cookierisk should show as connected.
Add --scope user to make it available in every project, not just this one.
Claude Desktop
- Open Customize → Connectors, click + Add, then Add custom connector.
- Name it CookieRisk and paste this URL:
https://cookierisk.eu/mcp- Click Add. Its tools appear in the chat’s tools menu.
Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.
claude.ai
- Open the connector form on claude.ai. This button fills in the name and URL for you:
Add to claude.ai (opens in a new tab)
- Check that the URL reads
https://cookierisk.eu/mcpand click Add. - Turn it on in a chat from the tools menu.
Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under Organization settings → Connectors.
ChatGPT
- On chatgpt.com, go to Plugins, select +, then Add custom MCP server.
- Enter a name for the server.
- Under Connection, paste
https://cookierisk.eu/mcpas the server URL, then for authentication choose No authentication. - Check I understand and want to continue, then select Create as a plugin.
Whether you can add a custom MCP server depends on your ChatGPT plan and your workspace permissions (in Business workspaces, admins and owners can).
Cursor
Add to Cursor (opens in a new tab)
Or add it by hand to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (this project):
{
"mcpServers": {
"cookierisk": {
"url": "https://cookierisk.eu/mcp"
}
}
}VS Code
Install in VS Code (opens in a new tab)
Or from a terminal:
code --add-mcp '{"name":"cookierisk","type":"http","url":"https://cookierisk.eu/mcp"}'Or commit it to the repo in .vscode/mcp.json:
{
"servers": {
"cookierisk": {
"type": "http",
"url": "https://cookierisk.eu/mcp"
}
}
}Devin Desktop
- Add it to
~/.config/devin/mcp_config.json(macOS and Linux) or%APPDATA%\devin\mcp_config.json(Windows):
{
"mcpServers": {
"cookierisk": {
"serverUrl": "https://cookierisk.eu/mcp"
}
}
}- Refresh the MCP server list in Cascade.
Devin Desktop is the new name for Windsurf. It reads serverUrl (or url) for remote servers.
Codex
codex mcp add cookierisk --url https://cookierisk.eu/mcpOr edit ~/.codex/config.toml directly:
[mcp_servers.cookierisk]
url = "https://cookierisk.eu/mcp"Gemini CLI
gemini mcp add --transport http cookierisk https://cookierisk.eu/mcpThis adds it to the current project. Add -s user to use it everywhere.
Any client
Most clients accept this shape. Some name the URL field differently: serverUrl in Devin Desktop, httpUrl in Gemini CLI’s settings file.
{
"mcpServers": {
"cookierisk": {
"type": "http",
"url": "https://cookierisk.eu/mcp"
}
}
}Zed puts servers under context_servers in its settings. Cline needs "type": "streamableHttp", or it assumes SSE.
Client only starts local servers? Bridge it with npx -y mcp-remote https://cookierisk.eu/mcp.
Embed
Show CookieRisk in a README or on your site. Each embed links to this page, uses the server’s own URL, and sets no cookies. How embeds work
The card, the iframe and the JSON are in English. Add ?lang=it, fr, de or es to their address for another language.
README badge
[](https://mcp.tc/i/cookierisk)<a href="https://mcp.tc/i/cookierisk"><img src="https://mcp.tc/i/cookierisk/badge.svg" alt="CookieRisk on mcp.tc" height="20"></a>It follows the reader’s light or dark mode. Add ?theme=light or ?theme=dark to fix it, or ?style=compact to show the mark without the word.
Website card
<script src="https://mcp.tc/w/cookierisk.js" async></script>The card appears where the tag is. Add data-theme="dark" or data-size="compact" to the tag to change it. The file holds everything it needs, so it makes no other requests and sets no cookies.
iframe
<iframe src="https://mcp.tc/embed/cookierisk" title="CookieRisk on mcp.tc" width="420" height="200" loading="lazy" allow="clipboard-write" style="border:0;border-radius:8px;max-width:100%"></iframe>Use it on pages that don’t allow scripts. Add ?theme=light or ?theme=dark to the address to fix the colors.
JSON
The listing as data for your own pages and tools: name, tagline, the server’s own URL, tools and the “Add to” links. Any site can read it (CORS is open).
https://mcp.tc/i/cookierisk.jsonAI prompt
Paste this into an AI coding assistant, such as Claude Code or Cursor, and it adds the CookieRisk card to your site.
Add the mcp.tc card for CookieRisk, an MCP server, to my website. It is one static script: no build step, no package to install, no cookies.
Put this tag where the card should appear. The card renders right before it:
```html
<script src="https://mcp.tc/w/cookierisk.js" async></script>
```
To show the card somewhere else, put this placeholder there and load the same script once, for example before `</body>`. Keep the link inside: visitors without JavaScript see it.
```html
<div data-mcptc="cookierisk"><a href="https://mcp.tc/i/cookierisk">CookieRisk on mcp.tc</a></div>
```
Options:
- `data-theme="light"` or `"dark"` on the tag or the placeholder fixes the colors. Without it, the card follows the visitor’s light or dark mode.
- `data-size="compact"` gives a smaller card without the tagline.
- The CSS variable `--mcptc-max-width` on the placeholder or a parent sets the width (default `520px`).
- `?lang=` on the script URL sets the card’s language: `en`, `it`, `fr`, `de` or `es`.
If the site has a Content Security Policy, allow `script-src https://mcp.tc` and `img-src data:` (the icon is inline).
For a README or other Markdown docs, use the badge instead:
```markdown
[](https://mcp.tc/i/cookierisk)
```
Reference: https://mcp.tc/embedChange history
We read this server’s tool list every 3 hours and record what changes. Last read 18 Nov 2026, 02:47 UTC.
-
2 tools changed. Server instructions changed.
New server instructions
Details, 9 Nov 2026, 17:51 UTC
Changed 2
get_quickscan_resultdescription, input schema and hintsBeforeUse the scanId returned by start_quickscan to retrieveprogress or sanitizedfindings, includingthe visible banner provider and controls, CookieRisk score, pre-consent tracking status, tag or service classifications, browser-recorded initiatorhostsand consentsignals 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,incompleteand failed scans do not establish absence of tracking. Accept and reject behavior is outside the scan scope.AfterRetrieves 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.
- Description of
scanIdBeforeThe
scanId returned by start_quickscan.AfterThe identifier of a CookieRisk quickscan.
- Description of
start_quickscandescription and hintsBeforeUse this whenauser asks to checka publicwebsitehomepage for cookies and tracking observed beforeinteraction. Createsa scan andvisitsthewebsite. Only submit the homepage URL; do not use forprivate pages, legal verdicts, accept/reject testing, monitoring,orbulk 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.AfterStarts 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.
Server instructions
Beforenone
AfterFor reused scans, immediately report evidenceCapturedAt when known and domainCooldownEndsAt. The cooldown end does not guarantee capacity for a new scan. Use the scanId from start_quickscan to read progress or results with get_quickscan_result. Wait pollAfterSeconds between reads and respect retryAfter on errors.
-
Tracking started: 2 tools.
FAQ
Can I paste mcp.tc/i/cookierisk into my MCP client?
No. mcp.tc links are pages, not server addresses. Connect with https://cookierisk.eu/mcp, so your client talks to CookieRisk directly. The quick link is for sharing: it opens this page, with setup steps for every client.
Does CookieRisk need an API key or a sign-in?
No. CookieRisk doesn’t ask for an account or key.
Is CookieRisk a remote or a local server?
Remote. CookieRisk hosts it at https://cookierisk.eu/mcp, and it speaks Streamable HTTP. There’s nothing to install.
What can CookieRisk do?
It has 2 tools: start_quickscan and get_quickscan_result. You can start a quickscan of a public website homepage, poll scan progress and read sanitized findings and see the visible cookie banner provider and controls.
Which clients can use it?
Any client that supports remote MCP servers: Claude Code, Claude Desktop, claude.ai, ChatGPT, Cursor, VS Code, Devin Desktop, Codex, Gemini CLI, Zed and others. The setup steps cover each one.
Does mcp.tc track changes to CookieRisk?
Yes. CookieRisk’s History tab shows each change we find to its tools, down to descriptions and parameters, plus new versions and edits by its owner. Follow the listing to get an email when it changes.
Who wrote this page?
mcp.tc’s robot read CookieRisk’s own metadata (its MCP handshake, tool list and public pages), and an AI model drafted the text from it. A person reviews anything the checks can’t confirm. The text can still be wrong, so if you spot a mistake, use Report this listing on this page.
mcp.tc isn’t affiliated with CookieRisk. This page was built from CookieRisk’s public metadata, last checked on 18 Nov 2026, and an AI model wrote the description, so it can be wrong. Names and marks belong to their owners. Something off? Report this listing.