Check what a site's cookie banner really blocks: CMP, trackers, cookies before consent.
Connect Remote server
claude mcp add --transport http cookieinspector https://api.cookieinspector.com/mcp
{
"mcpServers": {
"cookieinspector": {
"url": "https://api.cookieinspector.com/mcp"
}
}
}
{
"servers": {
"cookieinspector": {
"type": "http",
"url": "https://api.cookieinspector.com/mcp"
}
}
}
Settings > Connectors > Add custom connector
URL: https://api.cookieinspector.com/mcp
Tools 9 found in our last check
get_scan_summarySummary 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.
get_scan_statusStatus 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.
get_prescan_resultReturn 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…
start_scanStart 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 ge…
get_capabilitiesDescribe 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 u…
list_scansThe 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.
get_scan_findingsThe 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.
explain_findingExplain 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.
prescan_siteStart 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…
Details
| Endpoint | https://api.cookieinspector.com/mcp (Streamable HTTP) |
| First published | 19 Oct 2026 |
| Last updated | 19 Oct 2026 |
| Registry name | com.cookieinspector/cookieinspector |
More security servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
