The CookieInspector MCP server,
connected in one click.
Check what a site's cookie banner really blocks: CMP, trackers, cookies before consent. Connect the official CookieInspector MCP server to Claude, ChatGPT, or Cursor through gate — one gateway URL, no config files, security-checked.
Free to start · No credit card · No hosting needed
Add CookieInspector to your AI in one minute
Pick your client. Copy, paste, done — or let gate handle sign-ins and policies for you.
claude mcp add --transport http cookieinspector https://api.cookieinspector.com/mcpRun in your terminal, then restart Claude Code.
CookieInspector · https://api.cookieinspector.com/mcp
What your AI can do with CookieInspector
Real prompts you can type the moment it's connected — no setup, no docs to read.
“Use “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 track.”
“Use “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.”
“Use “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.”
“Use “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.”
How secure is the CookieInspector MCP server?
Every server in the gate directory has to pass the same four checks before your AI can touch it. Here's how CookieInspector holds up.
Security grade B
gate scanned 9 tools on Oct 21, 2026. A few things are worth a look before you connect.
- mediumget_capabilities: References secrets or data exfiltration
Official endpoint
Operated by CookieInspector (cookieinspector.com) at its documented MCP endpoint — not a third-party mirror or community re-host.
No sign-in needed
This server only exposes public data — no account and no credentials are involved when you connect.
Scanned before it goes live
gate checks every tool for prompt injection, hidden instructions, data-exfiltration hints, and over-broad permissions before the server is available through your gateway.
Watched for drift
If CookieInspector adds or changes tools later, gate re-scans and alerts you — before your AI acts on the change.
Connected in three steps
Connect your gate
Add one gateway URL to Claude, ChatGPT, or any MCP client. One-time setup, about two minutes.
Pick CookieInspector
Choose CookieInspector in the gate directory. No sign-in needed.
Use it anywhere
CookieInspector's tools are live in every AI client you've connected — with rules and logging built in.
Free to start · No credit card · No hosting needed
The actual tools CookieInspector exposes
Fetched live from the official endpoint and re-checked daily by gate — not marketing copy.
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 track
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
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
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
get_capabilities — Describe what CookieInspector checks on a website (cookies and trackers before and after the consent click, banner behaviour, consent platfo
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, no
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
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 netw
+ 1 more tools once connected
Who runs the CookieInspector MCP server?
The CookieInspector MCP server at a glance
https://api.cookieinspector.com/mcpQuestions, answered
Is there an official CookieInspector MCP server?
Yes — CookieInspector operates its own remote MCP server at api.cookieinspector.com. gate connects you to that official endpoint and adds security scanning, per-tool access rules, and an activity log on top.
How do I connect CookieInspector to Claude or ChatGPT?
Add gate's gateway URL to your AI client once, then pick CookieInspector in the directory. No account or sign-in is needed. From then on, CookieInspector's tools are available in every client you've connected to gate.
Do I need to host anything?
No. CookieInspector runs the server, and gate is fully managed. You just connect one URL — there's nothing to install, deploy, or maintain.
Is the CookieInspector MCP server safe to connect?
It's the vendor's official endpoint, and gate scans its tools for prompt injection and hidden instructions before it goes live, re-checks it whenever it changes, and lets you allow, block, or require approval for every single tool.
Is it free?
Yes — you can get started with gate for free and connect CookieInspector in minutes. No credit card required.
Connect more than just CookieInspector
Every server below works through the same gateway URL — connect once, add tools anytime.
Squarespace DomainsDesignView →Set up CookieInspector in: Claude · Claude Code · ChatGPT · Cursor · VS Code
Give your AI CookieInspector — safely.
One URL. All MCPs. Full control. Free to start.
Get started free