INDIVIDUAL MCP TOOL

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 account, which need a CookieInspector API key, and the quotas.

cookieinspector.comnone authenticationAvailability not checked

LIVE ENDPOINT

https://api.cookieinspector.com/mcp

No auth detected

Connect to this endpoint to inspect the live schema for get_capabilities and invoke it with your own arguments.

Indexed input schema

{}

Risk classification

Inferred read-only · medium confidence · heuristic, not a guarantee.

A tool name, description or schema mentions credentials.
A tool name or description suggests retrieving external content.

Parent server

cookieinspector.com

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.cookieinspector]
url = "https://api.cookieinspector.com/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "cookieinspector": {
      "type": "http",
      "url": "https://api.cookieinspector.com/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: cookieinspector
Remote MCP URL: https://api.cookieinspector.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "cookieinspector": {
      "url": "https://api.cookieinspector.com/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "cookieinspector": {
      "type": "http",
      "url": "https://api.cookieinspector.com/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "cookieinspector",
  "transport": "streamable-http",
  "url": "https://api.cookieinspector.com/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

Related tools

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.
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.
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 name, the consent platform and its confidence, Google Consent Mode status, three findings, and the report link.
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.
list_scans — The most recent scans on the connected account, newest first (up to 20), each with its riskScore (0 best, 100 worst).
get_scan_findings — The findings of a scan on the connected account, with severity, the affected resource and the recommendation, up to 25.
explain_finding — Explain a CookieInspector finding code (e.
prescan_site — Start a quick, anonymous pre-scan of a public website's home page: HTTP headers and HTML only, no real browser.