Security & Testing

cookieinspector.com

Scans websites to detect cookies and trackers before and after consent, reporting privacy risk and consent compliance.

1 endpoint9 known toolsFirst detected October 20, 2026Last detected October 20, 2026

ENDPOINT 1

https://api.cookieinspector.com/mcp

No auth detected

MCP server metadata

Name: CookieInspector
Version: 1.0.0

Capabilities

loggingtools

Known tools 9

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.

Inferred read-only

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.

Inferred read-only

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.

Inferred read-only

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.

Inferred read-only

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.

Inferred read-only

list_scans

The most recent scans on the connected account, newest first (up to 20), each with its riskScore (0 best, 100 worst).

Inferred read-only

get_scan_findings

The findings of a scan on the connected account, with severity, the affected resource and the recommendation, up to 25.

Inferred read-only

explain_finding

Explain a CookieInspector finding code (e.

Inferred read-only

prescan_site

Start a quick, anonymous pre-scan of a public website's home page: HTTP headers and HTML only, no real browser.

Inferred read-only

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.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.