Cookie Consent Compliance Scanner MCP Server

io.github.vincentn-waivern/cookie-checker-gdpr-ccpa-gcmv2

answering

Cookie Consent Compliance Scanner is answering right now. Last checked 8 min ago. It exposes 6 tools.

Cookie consent scanner: GDPR, CCPA, GCMv2. PASS/FAIL compliance checklists with fix recommendations.

The linked repository no longer exists on GitHub — it was deleted or made private.

Uptime history 39 hours of history

39 hours agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

245 ms

Response time

average over 24h

open, no key

Access

streamable-http

Connect this server

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

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add cookie-checker-gdpr-ccpa-gcmv2 --transport http https://consent-analyser-emea.waivern.com/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "cookie-checker-gdpr-ccpa-gcmv2": {
      "url": "https://consent-analyser-emea.waivern.com/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.cookie-checker-gdpr-ccpa-gcmv2]
url = "https://consent-analyser-emea.waivern.com/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "cookie-checker-gdpr-ccpa-gcmv2": {
      "url": "https://consent-analyser-emea.waivern.com/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "cookie-checker-gdpr-ccpa-gcmv2": {
      "url": "https://consent-analyser-emea.waivern.com/mcp"
    }
  }
}

Available tools 6

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

scan

get_scan_report

Retrieve the compliance report for a completed scan. Always call get_scan_status first to confirm done=True. For a focused view of what needs fixing, prefer get_failing_checks instead.

get_scan_status

Check whether a scan is still running. Poll this every 10–15 seconds after calling scan_url. When done=True, call get_scan_report or get_failing_checks to retrieve results.

scan_url

Start a cookie consent compliance scan on the given URL. The scan runs asynchronously in the background. This tool returns a run_id immediately — the actual scan takes 60–120 seconds. Use get_scan_status(run_id) to poll for completion, then call get_scan_report(run_id) or get_failing_checks(run_id). If login_username and login_password are supplied, a paired scan is run: one scan before login and one after, linked by a scan_group_id. The returned run_id is for the pre-login scan. Only one credit is consumed.

failing

get_failing_checks

Return only the FAIL and PARTIAL checks from a completed scan. This is the most useful tool for an agent writing a compliance summary or remediation plan — it omits all the passing checks and focuses entirely on what needs to be fixed, with actionable recommendations for each issue.

payment

get_payment_link

Get a Stripe payment link to buy 50 scan credits for $5. Returns a URL that the user should open in their browser to complete the payment. Credits are added to their account automatically once payment is confirmed — usually within a few seconds. Requires a valid bearer token (anonymous callers cannot purchase).

scans

list_my_scans

List your recent scans (or recent public scans if anonymous). Returns scans ordered most-recent first. Use the run_id from any row to retrieve the full report with get_scan_report or get_failing_checks.

Endpoints

URL	Transport	State	Latency	Checked
https://consent-analyser-emea.waivern.com/mcp	streamable-http	answering	218 ms	8 min ago

Cookie Consent Compliance Scanner — questions

Answers built from our own checks of this server.

What can Cookie Consent Compliance Scanner do?

It exposes 6 tools, read directly from the server on our last check. Among them: get_failing_checks, get_payment_link, get_scan_report, get_scan_status, list_my_scans, scan_url. 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 Cookie Consent Compliance Scanner 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 245 ms. The bar chart above shows every period we have measured.

Is Cookie Consent Compliance Scanner still maintained?

The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.

How do I connect Cookie Consent Compliance Scanner?

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

Does Cookie Consent Compliance Scanner need an API key?

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

How fast is Cookie Consent Compliance Scanner?

It answers our handshake in 245 ms on average, which is faster than 54% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.