Cookie Consent Compliance Scanner
REMOTE · CONSENT-ANALYSER-EMEA.WAIVERN.COM
Cookie consent scanner: GDPR, CCPA, GCMv2. PASS/FAIL compliance checklists with fix recommendations.
Available components
Last scanned (22 hours ago)
Scores higher than 8% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Security
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 404. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 15 Aug 26 0
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.63 → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 7 Aug 26 0
- The server no longer declares the “experimental” capability functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Probed https://consent-analyser-emea.waivern.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=consent-analyser-emea.waivern.com | CN=YE2,O=Let's Encrypt,C=US | 8 Oct 2026 | 6 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 6d15783565aebee0c0130fd54a164832dee |
| SANs: consent-analyser-emea.waivern.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of consent-analyser-emea.waivern.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| waivern.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 404 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://consent-analyser-emea.waivern.com/mcp | HTTP error | 404 | |
| http (plaintext) | http://consent-analyser-emea.waivern.com/mcp | HTTPS enforced | 301 | https://consent-analyser-emea.waivern.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_failing_checks ~90
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.
| Name | Type | Req | Description |
|---|---|---|---|
| run_id | string | yes | The 8-character run_id returned by scan_url. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
get_payment_link ~76
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).
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| credits | integer | yes | Number of scan credits included in this purchase. |
| message | string | yes | Human-readable instruction to share with the user. |
| price_usd | number | yes | Price in USD. |
| url | string | yes | Stripe Checkout URL. Open this in a browser to complete payment. |
No examples provided.
get_scan_report ~111
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.
| Name | Type | Req | Description |
|---|---|---|---|
| run_id | string | yes | The 8-character run_id returned by scan_url. |
| summary_only | boolean | – | If True, return only the headline score and per-check PASS/FAIL list without verbose detail. Useful for a quick overview or when token budget is limited. Default false (full report). |
| Name | Type | Req | Description |
|---|---|---|---|
| checks | – | – | Per-check PASS/FAIL list (summary mode). |
| mode | – | yes | Compliance framework used. |
| report | – | – | Complete report object including full checklist, score, metadata, and AI narrative (full mode). |
| run_id | string | yes | 8-character scan identifier. |
| score | – | – | Overall compliance score 0–100 (summary mode). |
| score_label | – | – | Score band e.g. 'Good', 'Needs Work', 'Critical' (summary mode). |
| started_at | – | yes | ISO 8601 timestamp when the scan started. |
| url | – | yes | Scanned URL. |
No examples provided.
get_scan_status ~68
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.
| Name | Type | Req | Description |
|---|---|---|---|
| run_id | string | yes | The 8-character run_id returned by scan_url. |
| Name | Type | Req | Description |
|---|---|---|---|
| c3_available | – | – | True if a C3 HTML detail report is available (present when done successfully). |
| cancelled | – | – | True if the scan was cancelled (present when done). |
| current_step | – | – | Most recent progress message (present while running). |
| done | boolean | yes | True when the scan has finished (success or failure). |
| elapsed_seconds | – | – | Seconds elapsed since scan started (present while running). |
| failed | – | – | True if the scan failed or was not found (present when done). |
| note | – | – | Human-readable note when the run is not found. |
No examples provided.
list_my_scans ~82
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of scans to return. Must be between 1 and 100. Default 20. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
scan_url ~383
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.
| Name | Type | Req | Description |
|---|---|---|---|
| ai_enhanced | boolean | – | Enable Claude AI narrative analysis layered on top of the automated checklist. Produces richer recommendations but takes longer and consumes Claude API credits. Default false. |
| login_password | – | – | Optional. Password for the login_username. Required if login_username is provided. |
| login_url | – | – | Optional. URL of the login page. If omitted, the scan target URL is used as the login page. |
| login_username | – | – | Optional. Username or email address to log in to the site before scanning. When provided together with login_password, two linked scans are run: one before login and one after. Only one credit is con… |
| mode | string | – | Compliance framework to audit against: 'gdpr' (GDPR/ePrivacy, default), 'ccpa' (US/CCPA), or 'gcm' (Google Consent Mode v2). |
| region | string | – | Geographic location of the probe browser: 'eu' (European IP, default) or 'us' (US IP via proxy). Use 'eu' unless you specifically need a US perspective. |
| url | string | yes | The website URL to scan, e.g. 'https://example.com'. HTTP is accepted and upgraded to HTTPS automatically. |
| Name | Type | Req | Description |
|---|---|---|---|
| mode | string | yes | Compliance framework in use: 'gdpr', 'ccpa', or 'gcm'. |
| note | string | yes | Reminder to poll get_scan_status every 10–15 s. |
| paired_run_id | – | – | Present only for paired scans. The run_id of the complementary (post-login) scan. |
| region | string | yes | Probe region: 'eu' or 'us'. |
| run_id | string | yes | 8-character identifier for this scan run. Pass to get_scan_status / get_scan_report. |
| scan_group_id | – | – | Present only for paired pre/post-login scans. Links the two runs together. |
| status | string | yes | Always 'started'. |
| url | string | yes | The normalised URL being scanned. |
No examples provided.
How do I install the Cookie Consent Compliance Scanner MCP server?
Cookie Consent Compliance Scanner is a hosted endpoint at https://consent-analyser-emea.waivern.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · consent-analyser-emea.waivern.com
claude mcp add --transport http vincentn-waivern-cookie-checker-gdpr-ccpa-gcmv2 'https://consent-analyser-emea.waivern.com/mcp'
What is the Cookie Consent Compliance Scanner MCP server?
Cookie Consent Compliance Scanner is an MCP server listed in the public MCP registry as io.github.vincentn-waivern/cookie-checker-gdpr-ccpa-gcmv2. Cookie consent scanner: GDPR, CCPA, GCMv2. PASS/FAIL compliance checklists with fix recommendations. This page covers its hosted endpoint (https://consent-analyser-emea.waivern.com/mcp).
Is the Cookie Consent Compliance Scanner MCP server safe to use?
Cookie Consent Compliance Scanner scores 23 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Cookie Consent Compliance Scanner MCP server expose?
Cookie Consent Compliance Scanner exposes 6 tools: scan_url, get_scan_status, get_scan_report, get_failing_checks, list_my_scans, get_payment_link. Their descriptions and schemas cost roughly 810 tokens of context every time the server is loaded.
Does the Cookie Consent Compliance Scanner MCP server require authentication?
Its publisher declares no required credentials for Cookie Consent Compliance Scanner. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Cookie Consent Compliance Scanner MCP server still maintained?
Cookie Consent Compliance Scanner is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.