CookieInspector

Ingested from the official MCP Registry

FastDrop pulled this entry from the official MCP Registry as com.cookieinspector/cookieinspector and probed the endpoint. The maker did not submit it, so the outbound link is not endorsed and the description is not theirs.

If this is your server, claim the listing to edit it and take ownership. The registry index lists everything else still awaiting a probe.

Tools this endpoint exposes

Read directly from the endpoint on 19 Oct 2026. Not supplied by the maker.

• get_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 fin

• get_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.

• get_prescan_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 na

• start_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-tar

• get_capabilities

  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 accoun

• list_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.

• get_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.

• explain_finding

  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.

Is this tool yours?

Claim this listing and we’ll verify ownership before handing it over.