# CookieRisk MCP server

> Scan a public website homepage for cookies and tracking that fire before consent and read the resulting findings.

- Listing: https://mcp.tc/i/cookierisk
- Connect: use the server's own URL `https://cookierisk.eu/mcp` (no sign-in); clients connect to it directly. The listing link is a page, not an MCP endpoint.
- Type: remote (Streamable HTTP)
- Auth: none
- Category: [Security & Compliance](https://mcp.tc/c/security)
- Vendor: CookieRisk
- Homepage: <https://cookierisk.eu/>

## About

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 it 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_quickscan`: Create a quickscan for a public homepage URL and return a scanId and polling interval.
- `get_quickscan_result`: Read progress or sanitized findings for a scan by scanId, including score and tracking status. (read-only)

## 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."

## Install

### Claude Code

1. Run this in a terminal, in your project folder:

```bash
claude mcp add --transport http cookierisk https://cookierisk.eu/mcp
```

2. 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

1. Open **Customize → Connectors**, click **+ Add**, then **Add custom connector**.

2. Name it **CookieRisk** and paste this URL:

```url
https://cookierisk.eu/mcp
```

3. 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

1. Open the connector form on claude.ai. This button fills in the name and URL for you:

[Add to claude.ai](<https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=CookieRisk&connectorUrl=https%3A%2F%2Fcookierisk.eu%2Fmcp>) (opens connector settings)

2. Check that the URL reads `https://cookierisk.eu/mcp` and click **Add**.

3. 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

1. On chatgpt.com, go to **Plugins**, select **+**, then **Add custom MCP server**.

2. Enter a name for the server.

3. Under **Connection**, paste `https://cookierisk.eu/mcp` as the server URL, then for authentication choose **No authentication**.

4. 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](<https://cursor.com/install-mcp?name=cookierisk&config=eyJ1cmwiOiJodHRwczovL2Nvb2tpZXJpc2suZXUvbWNwIn0%3D>) (opens Cursor)

Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project):

`mcp.json`:

```json
{
  "mcpServers": {
    "cookierisk": {
      "url": "https://cookierisk.eu/mcp"
    }
  }
}
```

### VS Code

[Install in VS Code](<https://vscode.dev/redirect/mcp/install?name=cookierisk&config=%7B%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Fcookierisk.eu%2Fmcp%22%7D>) (opens VS Code)

Or from a terminal:

```bash
code --add-mcp '{"name":"cookierisk","type":"http","url":"https://cookierisk.eu/mcp"}'
```

Or commit it to the repo in `.vscode/mcp.json`:

`.vscode/mcp.json`:

```json
{
  "servers": {
    "cookierisk": {
      "type": "http",
      "url": "https://cookierisk.eu/mcp"
    }
  }
}
```

### Devin Desktop

1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows):

`mcp_config.json`:

```json
{
  "mcpServers": {
    "cookierisk": {
      "serverUrl": "https://cookierisk.eu/mcp"
    }
  }
}
```

2. Refresh the MCP server list in Cascade.

Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers.

### Codex

```bash
codex mcp add cookierisk --url https://cookierisk.eu/mcp
```

Or edit `~/.codex/config.toml` directly:

`config.toml`:

```toml
[mcp_servers.cookierisk]
url = "https://cookierisk.eu/mcp"
```

### Gemini CLI

```bash
gemini mcp add --transport http cookierisk https://cookierisk.eu/mcp
```

This 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.

```json
{
  "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`.

## Recent changes

- 2026-11-09 17:51 UTC: 2 tools changed. Server instructions changed. Source: automatic check. Worth a look: new server instructions. Changed: get\_quickscan\_result, start\_quickscan.
- 2026-11-09 11:27 UTC: Tracking started: 2 tools read. Source: automatic check.

More on the History tab, with descriptions before and after for the newest entries: https://mcp.tc/i/cookierisk#history (Atom feed: https://mcp.tc/i/cookierisk/history.xml). It records what mcp.tc's anonymous checks saw, every 3 hours where the tool list can be read without sign-in; it is not a security review.

## Details

- Server version: 1.0.0
- MCP protocol version: 2025-11-25
- Last checked: 2026-11-18 (reachable)
- Listed: 2026-11-09
- Updated: 2026-11-09

---
Source: https://mcp.tc/i/cookierisk (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report
