CookieRisk Quickscan MCP Server

by cookierisk Your server? Claim it

answering

CookieRisk Quickscan is answering right now. Last checked 14 min ago. It exposes 2 tools.

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

Uptime history 26 hours of history

26 hours agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

627 ms

Response time

average over 24h

open, no key

Access

streamable-http

Nothing serious here today

Today is the operative word: we check CookieRisk Quickscan every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 14 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

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

Settings → Connectors → Add custom connector, then paste this address

https://cookierisk.eu/mcp

~/.codex/config.toml

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

.cursor/mcp.json

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

.vscode/mcp.json

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

Available tools 2

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

quickscan

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.

start

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.

Endpoints

URL	Transport	State	Latency	Checked
https://cookierisk.eu/mcp	streamable-http	answering	408 ms	14 min ago

Alternatives to CookieRisk Quickscan

same job, measured the same way

Delta Witness

by 15998194110

Paid Capture and Guard tools for public-source observations before autonomous actions.

65 installs/wk local only

BHG Site Tracking Check

by bhgsupport

Checks a public web page in a real browser for analytics and ad conversion tags. No key needed.

1 tools answering

Heimdall

by caglarbozkurt

Scan an MCP server or agent config for injection, exfiltration, and risky capabilities.

70 installs/wk local only

Spain Legal by Legal Fournier

by legalfournier

Spain legal screening, articles, videos, interactive apps, public skills, and consent-based contact.

13 tools answering

Pre-transaction Safety Checks (Tanod)

by tanod

Safety checks before you sign, pay or install: contract, token and package scans, phishing, OFAC.

28 tools answering

AI Home Services Booking

by aihomeservices

Agent-first booking of home-service contractors in Canada and the US: quotes, availability, booking.

3 tools answering

HVTracker MCP

by yugantm

Pre-connect trust checks for AI agents and MCP servers using HVTracker's public trust registry.

155 installs/wk 8 tools answering

Ticktick MCP

by partymola

MCP server for TickTick task management: field-preserving updates and completion tracking.

local only

CookieRisk Quickscan — questions

Answers built from our own checks of this server.

What can CookieRisk Quickscan do?

It exposes 2 tools, read directly from the server on our last check. Among them: get_quickscan_result, start_quickscan. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is CookieRisk Quickscan working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 627 ms. The bar chart above shows every period we have measured.

How do I connect CookieRisk Quickscan?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does CookieRisk Quickscan need an API key?

No. CookieRisk Quickscan completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 2 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is CookieRisk Quickscan?

It answers our handshake in 627 ms on average, which is faster than 16% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.