CookieInspector
REMOTE · API.COOKIEINSPECTOR.COM
Check what a site's cookie banner really blocks: CMP, trackers, cookies before consent.
Available components
Last scanned (23 hours ago)
Scores higher than 79% 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 Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- 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 & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 833 tokens (~92/item across 9 items; 9 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management53
- Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
- 3 Nov 26 +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.
- 1 Nov 26 +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.
- 30 Oct 26 +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.
- 27 Oct 26 +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.
- 25 Oct 26 +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.
- 23 Oct 26 +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.
- 21 Oct 26 +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.
- 20 Oct 26 0
- Stability: unverified → 0.03 ▲ 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://api.cookieinspector.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.cookieinspector.com | CN=GeoTrust TLS RSA CA G1,OU=www.digicert.com,O=DigiCert Inc,C=US | 11 Oct 2026 | 11 Apr 2027 | RSA 2048 | SHA256-RSA | 105e5fe1850b46f2a633917acdafe5e |
| SANs: api.cookieinspector.com | ||||||
| CN=GeoTrust TLS RSA CA G1,OU=www.digicert.com,O=DigiCert Inc,C=US (CA) | CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US | 2 Nov 2017 | 2 Nov 2027 | RSA 2048 | SHA256-RSA | d07782a133fc6f9a57296e131ffd179 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.cookieinspector.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| cookieinspector.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.cookieinspector.com/mcp | Verified | 200 | |
| http (plaintext) | http://api.cookieinspector.com/mcp | HTTPS enforced | 301 | https://api.cookieinspector.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 →
explain_finding Explain a finding or a consent platform ~88
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.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | A finding code from a report, such as COOKIES_BEFORE_CONSENT, or a consent platform name such as OneTrust |
No output schema declared.
No examples provided.
get_capabilities What CookieInspector can do here ~74
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_prescan_result Pre-scan result ~136
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.
| Name | Type | Req | Description |
|---|---|---|---|
| preScanId | string | yes | The preScanId returned by prescan_site |
No output schema declared.
No examples provided.
get_scan_findings Scan findings ~71
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.
| Name | Type | Req | Description |
|---|---|---|---|
| scanId | string | yes | The scanId returned by start_scan or list_scans |
No output schema declared.
No examples provided.
get_scan_status Scan status ~67
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.
| Name | Type | Req | Description |
|---|---|---|---|
| scanId | string | yes | The scanId returned by start_scan or list_scans |
No output schema declared.
No examples provided.
get_scan_summary Scan summary ~75
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.
| Name | Type | Req | Description |
|---|---|---|---|
| scanId | string | yes | The scanId returned by start_scan or list_scans |
No output schema declared.
No examples provided.
list_scans List recent scans ~68
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer|null | – | How many to return, 1 to 20. Default 10. |
No output schema declared.
No examples provided.
prescan_site Quick pre-scan of a website ~104
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.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The website to check, e.g. example.com or https://example.com |
No output schema declared.
No examples provided.
start_scan Start a full scan ~150
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.
| Name | Type | Req | Description |
|---|---|---|---|
| evaluateCcpa | boolean|null | – | Also evaluate CCPA/CPRA (California). Default true. |
| region | string|null | – | Scan location: main, us-west or eu-de |
| url | string | yes | The website to scan, absolute, e.g. https://example.com |
No output schema declared.
No examples provided.
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.
remote · api.cookieinspector.com
claude mcp add --transport http com-cookieinspector-cookieinspector 'https://api.cookieinspector.com/mcp'
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 79 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 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.