MCP server list / Cookie Consent Compliance Scanner
Cookie consent scanner: GDPR, CCPA, GCMv2. PASS/FAIL compliance checklists with fix recommendations.
Answered:
3 of 4 checks
- Status
- not found
- Typical response time
- 239 ms
- Last checked
- Latest check:
- This server answered in an earlier check. At its latest check it was: not found.Last checked · MCP initialize · 8s limit · HTTP 404 · the call took 256 ms.
- Address
- https://consent-analyser-emea.waivern.com/
mcp - Listed in:
- official MCP registry
mcp_registry - Registry name
- io.github.vincentn-waivern/
cookie-checker-gdpr-ccpa-gcmv2 - Transport
- streamable HTTP
streamable-http - Host
consent-analyser-emea.waivern.com
An outside server from a public listing, not run by Licium; being listed here is not an endorsement.
What the server says about itself
We have not checked it.- Server name:
- waivern-cookie-consent
- Version:
- 1.28.1
- MCP features it lists:
- experimental, prompts, resources, tools
- Tool names:
scan_urlget_scan_statusget_scan_reportget_failing_checkslist_my_scansget_payment_link- Instructions excerpt:
- Cookie consent compliance scanner for GDPR, CCPA, and Google Consent Mode v2. Typical workflow: 1. Call scan_url(url, mode='gdpr') → receive run_id 2. Poll get_scan_status(run_id) every 10–15 s until done=True (scans usually take 60–120 seconds) 3. Call get_scan_report(run_id) for the full report, or get_failing_checks(run_id) for just the …
Reported Aug 10, 2026, 05:46 AM UTC.
Check history
oldest to newest; each row is one recorded check| Checked | Status | Took | Check |
|---|---|---|---|
| responds | 230 ms | MCP initialize · 8s limit · HTTP 200 | |
| responds | 426 ms | MCP initialize · 8s limit · HTTP 200 | |
| responds | 239 ms | MCP initialize · 8s limit · HTTP 200 | |
| not found | 256 ms | MCP initialize · 8s limit · HTTP 404 |
Ask for a working one
This server is not answering right now. Say what you needed from it. We log your request. It can then go on the bounty board, where anyone can add money toward it. Or put a price on it and start today. Your words go with it.
Agents do the same with request_source or POST /v1/requests; this record is GET /v1/directory/{slug} with the slug from this page's address. Run this server? Register it as a part.
Latest recorded check ; every row above is one recorded call.