ZBS Index What actually exists in applied AI, with the source next to it

mcp server

Cookie Consent Compliance Scanner

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

Description as published by the maintainer. Source

  • version 2.0.0
  • active
  • security

active — Registry entry last updated 2026-05-24. Dashed tags are derived by ZBS Index from the published description, not stated by the maintainer.

What this server can do

6 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.

get_failing_checks(run_id)
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. Required: run_id.
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).
get_scan_report(run_id, summary_only)
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. Required: run_id.
get_scan_status(run_id)
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. Required: run_id.
list_my_scans(limit)
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.
scan_url(url, mode, region, login_url, ai_enhanced, login_password, login_username)
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. Required: url.

Last successful function declaration observed on . Source: https://consent-analyser-emea.waivern.com/mcp. We list what the server declared; we do not call any of these functions.

Endpoint status observed on . Source: https://consent-analyser-emea.waivern.com/mcp.

Signals

These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.

Signal Value What it measures Window Observed Source
Latest published version 2.0.0 Latest version string the maintainer published to the registry. as of fetch Model Context Protocol
Registry record last updated 2026-05-24 When the registry record was last updated by its maintainer. point in time Model Context Protocol
First listed in the MCP Registry 2026-05-24 Date this server was first published to the official MCP Registry. Not a usage or quality measure. point in time Model Context Protocol
mcp tools declared 6 tools Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. as of probe consent-analyser-emea.waivern.com
mcp endpoint status ok The server listed 6 functions when asked. as of probe consent-analyser-emea.waivern.com

Where to get it

This record as data

Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.

GET /api/v1/entries/mcp_server.json

Sources

  1. Tools declared by the MCP server at https://consent-analyser-emea.waivern.com/mcp — consent-analyser-emea.waivern.com, observed , trust tier 1.
  2. Official MCP Registry — Model Context Protocol, observed , trust tier 1.