Check what a website's cookie banner actually blocks and what trackers load before you consent.
Scans websites to reveal cookies and trackers that load before consent, identifies the consent platform, and rates privacy risk. Provides technical findings on banner behavior and Google Consent Mode status. Quick pre-scans are free; full scans with browser automation require an account.
Try asking Muse: "Check if a shopping site is tracking me before I accept its cookie banner."
Source: Found in the official MCP Registry (com.cookieinspector/cookieinspector) · First listed October 29, 2026
Each bar is one check, every 15 minutes. Green means it answered. Last checked 2 h ago.
What Muse can see: It does not ask you to sign in, so it cannot see your accounts. It only sees what Muse sends it from your request.
Before it acts: Read what Muse plans to do before you approve it, and remove the app from Muse when you stop using it.
musedirectory.ai is not part of Meta. More about how Muse handles your information
Not in Muse's Connectors list yet, but Muse can still use it. Copy the request below and paste it into Muse. Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.
https://api.cookieinspector.com/mcpNot in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse.
CookieInspector is a remote MCP server, so any assistant that can add a custom connector by link can use it. Same link, same tools.
In ChatGPT, open Settings, then Connectors (called Apps & Connectors on some accounts).
Under Advanced settings, switch on Developer mode. That is what lets you add a connector by link.
Choose Create, give it a name, paste the link as the MCP server URL, and save. If it needs a sign-in, ChatGPT asks for it here.
Start a chat, open the tools menu, pick the connector, and ask. ChatGPT asks before it runs a tool the first time.
Custom connectors need a paid ChatGPT plan, and on Team, Enterprise and Edu accounts only an admin can add them. Our "Working" label means the server answered us; it cannot tell whether your plan lets you add it. All connectors that work in ChatGPT
In Claude, open Settings, then Connectors.
Choose Add custom connector, give it a name, and paste the link.
If it needs a sign-in, Claude sends you to it. Then turn the connector on in a chat from the tools menu and ask.
Custom connectors are available on paid Claude plans; on Team and Enterprise accounts an admin may need to add them. Our "Working" label means the server answered us; it cannot tell whether your plan lets you add it. All connectors that work in Claude
https://api.cookieinspector.com/mcpResponse time at the last check: 1111ms. Worked in n/a of checks over 30 days.
Screened, no issues found
Screening looks for known threats and hidden instructions at the time of the check, and runs again weekly and whenever the tool list changes. It cannot see the server's code, so only connect what you need and review what Muse asks to do. How screening works.
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 fstart_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 getget_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 unlist_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 https://api.cookieinspector.com/mcpNot in Muse's Connectors list yet, but Muse can still use it. Paste this into Muse: "Use CookieInspector to help me. It is a free service with an MCP server at https://api.cookieinspector.com/mcp. It does not need an API key. Ask me before you share anything with it." Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.
At the last check (October 29, 2026, 15:16 UTC) the endpoint was working, answering in 1111ms. It is checked every 15 minutes.
It was screened on October 29, 2026 with the result "screened, no issues found". Screening checks the domain against threat feeds and reads the tools for hidden instructions and requests for passwords or card numbers. It cannot see the server's code, so grant only the access you need.
It exposes 9 tools, including get_scan_summary, get_scan_status, get_prescan_result, start_scan. For example, you could ask Muse: "Check if a shopping site is tracking me before I accept its cookie banner."
This listing was added from public sources (Found in the official MCP Registry (com.cookieinspector/cookieinspector)). If you build CookieInspector, claim it to correct the details and get your badge.
Paste this on your site or README. It always shows the latest check.
<a href="https://musedirectory.ai/connector/cookieinspector"><img src="https://musedirectory.ai/badge/cookieinspector.svg" alt="CookieInspector on musedirectory.ai" width="236" height="40"></a>