# CookieRisk Quickscan [Verified owner] [Health: Active]

**Category:** 🔒 Security  
**Repository:** https://cookierisk.eu/mcp  
**Views:** 1  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/cookierisk-quickscan

## Description
Scan a public homepage for cookies and tracking observed before consent interaction.

## Tools
Capabilities this server exposes over MCP:

- **start_quickscan** — 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.
- **get_quickscan_result** — 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.

## Claude Desktop Quick Installation
Remote MCP endpoint (confidence: medium). Install path inferred — verify against the README before running it. Add as a URL/SSE server in your client:

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

## Documentation

## What CookieRisk Quickscan does

CookieRisk Quickscan exposes CookieRisk's homepage scanning workflow through MCP. It examines a public homepage for cookies and tracking activity observed before consent interaction, giving an agent a way to request a scan and inspect its result without implementing the scanning API directly.

The service is designed for a single public homepage rather than a broad compliance or monitoring workflow. Its scope excludes private pages, legal determinations, accept/reject behavior testing, ongoing monitoring, and bulk scanning.

## How it works

An agent first calls `start_quickscan` with a public homepage. The response includes a scan ID. When recent evidence can be reused, the response can also identify when that evidence was collected and when the domain's cooldown period ends.

The agent then passes the scan ID to `get_quickscan_result`. That call can return scan progress or sanitized findings, depending on the scan state. Findings may include the visible consent-banner provider and controls, the CookieRisk score, whether tracking appeared before consent, classifications for tags or services, browser-recorded initiator hosts, and consent-related signals.

Page-level settings and scan-wide network signals are represented separately. A request associated with a tracking category is not, by itself, proof that tracking occurred. Likewise, an unknown, incomplete, or failed scan cannot be interpreted as evidence that the page has no tracking.

## Setup and configuration

Use the MCP endpoint at `https://cookierisk.eu/mcp` with an MCP-compatible client or agent runtime. The developer reference for the interface is available at `https://cookierisk.eu/developers/mcp`.

The workflow requires a public homepage and the scan ID returned by `start_quickscan`. Clients should be prepared to poll or request results while a scan is in progress, and should preserve the distinction between fresh scans and reused evidence.

## Tools and capabilities

- `start_quickscan` starts a scan of a public homepage or reuses recent evidence.
- `get_quickscan_result` retrieves progress or sanitized findings for a CookieRisk scan ID.
- Reports can include the detected banner provider and available consent controls.
- Results may include a CookieRisk score, pre-consent tracking status, tag or service classifications, initiator hosts, and consent signals.
- Scan responses can expose evidence timing and a domain cooldown end when those details are available.

## Limitations and notes

The scan covers observations before consent interaction. It does not test what happens after accepting or rejecting consent, issue legal verdicts, inspect private pages, perform bulk scans, or provide continuous monitoring.

Interpret results according to their state and scope. Tracking-category classification alone does not confirm a network request was tracking, and failed, incomplete, or unknown scans do not demonstrate an absence of tracking. Page settings and network-wide signals should be evaluated as separate result areas.

_Full upstream README: https://allmcps.com/mcp/cookierisk-quickscan/readme_