# Cookie Consent Compliance Scanner (remote · consent-analyser-emea.waivern.com)

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

- Trust score: 72/100 (medium)
- Change this week: +6
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `consent-analyser-emea.waivern.com`: 72/100 (this document), [markdown](https://verifymcp.io/servers/vincentn-waivern-cookie-checker-gdpr-ccpa-gcmv2/consent-analyser-emea.md), [page](https://verifymcp.io/servers/vincentn-waivern-cookie-checker-gdpr-ccpa-gcmv2/consent-analyser-emea)

## Channel facts

- Endpoint: `https://consent-analyser-emea.waivern.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `2.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 978 tokens (~163/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

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

### Codex

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

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "vincentn-waivern-cookie-checker-gdpr-ccpa-gcmv2": {
      "type": "remote",
      "url": "https://consent-analyser-emea.waivern.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add vincentn-waivern-cookie-checker-gdpr-ccpa-gcmv2 --url https://consent-analyser-emea.waivern.com/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  vincentn-waivern-cookie-checker-gdpr-ccpa-gcmv2:
    url: "https://consent-analyser-emea.waivern.com/mcp"
```

### Other

```json
{
  "mcpServers": {
    "vincentn-waivern-cookie-checker-gdpr-ccpa-gcmv2": {
      "type": "http",
      "url": "https://consent-analyser-emea.waivern.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-02 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 71, +3)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 68, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-28 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 66, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 66)

First indexed and scored.

## MCP tools (6)

### `scan_url` (~383 tokens)

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.

Input parameters:

- `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, required): The website URL to scan, e.g. 'https://example.com'. HTTP is accepted and upgraded to HTTPS automatically.

Output parameters:

- `mode` (string): Compliance framework in use: 'gdpr', 'ccpa', or 'gcm'.
- `note` (string): 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): Probe region: 'eu' or 'us'.
- `run_id` (string): 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): Always 'started'.
- `url` (string): The normalised URL being scanned.

### `get_scan_status` (~68 tokens)

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.

Input parameters:

- `run_id` (string, required): The 8-character run_id returned by scan_url.

Output parameters:

- `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): 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.

### `get_scan_report` (~111 tokens)

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.

Input parameters:

- `run_id` (string, required): 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).

Output parameters:

- `checks`: Per-check PASS/FAIL list (summary mode).
- `mode`: Compliance framework used.
- `report`: Complete report object including full checklist, score, metadata, and AI narrative (full mode).
- `run_id` (string): 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`: ISO 8601 timestamp when the scan started.
- `url`: Scanned URL.

### `get_failing_checks` (~90 tokens)

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.

Input parameters:

- `run_id` (string, required): The 8-character run_id returned by scan_url.

Output parameters:

- `result` (array)

### `list_my_scans` (~82 tokens)

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.

Input parameters:

- `limit` (integer): Maximum number of scans to return. Must be between 1 and 100. Default 20.

Output parameters:

- `result` (array)

### `get_payment_link` (~76 tokens)

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).

Output parameters:

- `credits` (integer): Number of scan credits included in this purchase.
- `message` (string): Human-readable instruction to share with the user.
- `price_usd` (number): Price in USD.
- `url` (string): Stripe Checkout URL. Open this in a browser to complete payment.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/vincentn-waivern-cookie-checker-gdpr-ccpa-gcmv2/consent-analyser-emea#diagnostics

## Score history

- 2026-08-03: 72
- 2026-08-02: 72
- 2026-08-01: 71
- 2026-07-31: 71
- 2026-07-30: 68
- 2026-07-29: 68
- 2026-07-28: 67
- 2026-07-27: 66
- 2026-07-26: 66

## Links

- Remote endpoint: https://consent-analyser-emea.waivern.com/mcp
- Repository: https://github.com/waivern-compliance/har-analyzer
- Changelog RSS feed: https://verifymcp.io/servers/vincentn-waivern-cookie-checker-gdpr-ccpa-gcmv2/consent-analyser-emea/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/vincentn-waivern-cookie-checker-gdpr-ccpa-gcmv2/consent-analyser-emea/changelog.json
- HTML version of this page: https://verifymcp.io/servers/vincentn-waivern-cookie-checker-gdpr-ccpa-gcmv2/consent-analyser-emea