# CookieInspector (remote · api.cookieinspector.com)

Check what a site's cookie banner really blocks: CMP, trackers, cookies before consent.

- Trust score: 80/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `api.cookieinspector.com`: 80/100 (this document), [markdown](https://verifymcp.io/servers/com-cookieinspector-cookieinspector/api.md), [page](https://verifymcp.io/servers/com-cookieinspector-cookieinspector/api)

## Channel facts

- Endpoint: `https://api.cookieinspector.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.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-11-05.

- **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**: 79/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 833 tokens (~92/item across 9 items; 9 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 57/100
  - Stability observed for 17 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.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the CookieInspector MCP server?

CookieInspector is a hosted endpoint at https://api.cookieinspector.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.

### Claude

```bash
claude mcp add --transport http com-cookieinspector-cookieinspector 'https://api.cookieinspector.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-cookieinspector-cookieinspector": {
      "url": "https://api.cookieinspector.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-cookieinspector-cookieinspector": {
      "type": "http",
      "url": "https://api.cookieinspector.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-cookieinspector-cookieinspector]
url = "https://api.cookieinspector.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-cookieinspector-cookieinspector": {
      "type": "remote",
      "url": "https://api.cookieinspector.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-cookieinspector-cookieinspector --url 'https://api.cookieinspector.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-cookieinspector-cookieinspector:
    url: "https://api.cookieinspector.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-cookieinspector-cookieinspector": {
      "Transport": "http",
      "Url": "https://api.cookieinspector.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-cookieinspector-cookieinspector -t streamable-http -u 'https://api.cookieinspector.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-cookieinspector-cookieinspector": {
      "type": "http",
      "url": "https://api.cookieinspector.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-11-05 (score 80, +1)

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

### 2026-11-03 (score 79, +1)

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

### 2026-11-01 (score 78, +1)

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

### 2026-10-30 (score 77, +1)

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

### 2026-10-27 (score 76, +1)

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

### 2026-10-25 (score 75, +1)

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

### 2026-10-23 (score 74, +1)

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

### 2026-10-21 (score 73, +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.

## MCP tools (9)

### `get_scan_summary` (~75 tokens)

Scan summary

Summary of a completed scan on the connected account: risk score (0 best, 100 worst), verdict, banner and consent platform, cookie and tracker counts, the top issues and the report link. Technical findings, not legal advice.

Input parameters:

- `scanId` (string, required): The scanId returned by start_scan or list_scans

### `get_scan_status` (~67 tokens)

Scan status

Status of a scan on the connected account: queued, running, completed or failed, with the riskScore (0 best, 100 worst) once done. Technical findings, not legal advice.

Input parameters:

- `scanId` (string, required): The scanId returned by start_scan or list_scans

### `get_prescan_result` (~136 tokens)

Pre-scan result

Return the result of a pre-scan started with prescan_site: riskScore (0 best, 100 worst, the same scale as the full report), risk level, how many cookies load before consent, up to five trackers by name, the consent platform and its confidence, Google Consent Mode status, three findings, and the report link. This is a header-and-HTML pre-scan, single page; the full scan with a real browser, evidence and fix guide requires a CookieInspector account. Technical findings, not legal advice.

Input parameters:

- `preScanId` (string, required): The preScanId returned by prescan_site

### `start_scan` (~150 tokens)

Start a full scan

Start a full CookieInspector scan with a real browser (before and after the consent click, up to 5 pages) on the connected account. Optional region: main (US East), us-west, eu-de (Germany, for EU-targeted banners). Uses the plan's monthly scans. Returns a scanId to poll with get_scan_status, then get_scan_summary. Technical findings, not legal advice.

Input parameters:

- `evaluateCcpa` (boolean|null): Also evaluate CCPA/CPRA (California). Default true.
- `region` (string|null): Scan location: main, us-west or eu-de
- `url` (string, required): The website to scan, absolute, e.g. https://example.com

### `get_capabilities` (~74 tokens)

What CookieInspector can do here

Describe what CookieInspector checks on a website (cookies and trackers before and after the consent click, banner behaviour, consent platform, Google Consent Mode), which tools work without an account, which need a CookieInspector API key, and the quotas. Call this first when unsure which tool to use. Technical findings, not legal advice.

### `list_scans` (~68 tokens)

List recent scans

The most recent scans on the connected account, newest first (up to 20), each with its riskScore (0 best, 100 worst). Technical findings, not legal advice.

Input parameters:

- `limit` (integer|null): How many to return, 1 to 20. Default 10.

### `get_scan_findings` (~71 tokens)

Scan findings

The findings of a scan on the connected account, with severity, the affected resource and the recommendation, up to 25. Use explain_finding for what a code means. Technical findings, not legal advice.

Input parameters:

- `scanId` (string, required): The scanId returned by start_scan or list_scans

### `explain_finding` (~88 tokens)

Explain a finding or a consent platform

Explain a CookieInspector finding code (e.g. THIRD_PARTY_PRE_CONSENT) or what to check in a named consent platform (e.g. Cookiebot). No network call. Technical findings, not legal advice.

Input parameters:

- `code` (string, required): A finding code from a report, such as COOKIES_BEFORE_CONSENT, or a consent platform name such as OneTrust

### `prescan_site` (~104 tokens)

Quick pre-scan of a website

Start a quick, anonymous pre-scan of a public website's home page: HTTP headers and HTML only, no real browser. Returns a preScanId to pass to get_prescan_result and a link to the report on cookieinspector.com. CookieInspector works alongside any consent platform; it checks what the banner actually does. Technical findings, not legal advice.

Input parameters:

- `url` (string, required): The website to check, e.g. example.com or https://example.com

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-cookieinspector-cookieinspector/api#diagnostics

## Score history

- 2026-11-05: 80
- 2026-11-04: 79
- 2026-11-03: 79
- 2026-11-02: 78
- 2026-11-01: 78
- 2026-10-31: 77
- 2026-10-30: 77
- 2026-10-29: 76
- 2026-10-28: 76
- 2026-10-27: 76
- 2026-10-26: 75
- 2026-10-25: 75
- 2026-10-24: 74
- 2026-10-23: 74
- 2026-10-22: 73
- 2026-10-21: 73
- 2026-10-20: 72
- 2026-10-19: 72

## Common questions

### What is the CookieInspector MCP server?

CookieInspector is an MCP server listed in the public MCP registry as com.cookieinspector/cookieinspector. Check what a site's cookie banner really blocks: CMP, trackers, cookies before consent. This page covers its hosted endpoint (https://api.cookieinspector.com/mcp).

### Is the CookieInspector MCP server safe to use?

CookieInspector scores 80 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 CookieInspector MCP server expose?

CookieInspector exposes 9 tools: get_scan_summary, get_scan_status, get_prescan_result, start_scan, get_capabilities, and 4 more. Their descriptions and schemas cost roughly 833 tokens of context every time the server is loaded.

### Does the CookieInspector MCP server require authentication?

No. We connected to CookieInspector without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the CookieInspector MCP server still maintained?

CookieInspector is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://api.cookieinspector.com/mcp
- Website: https://www.cookieinspector.com/developers/mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-cookieinspector-cookieinspector/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-cookieinspector-cookieinspector/api.json
- HTML version of this page: https://verifymcp.io/servers/com-cookieinspector-cookieinspector/api