Cookie Consent Audit MCP Server

Cookie Consent Audit MCP Server

An MCP server for the Mamba Labs Cookie Consent Audit actor on Apify. Send a domain or a list of domains. Each one is loaded from an EU address in fresh browser sessions, and you get back one row of consent signals per domain: the consent platform, reject on the first layer, trackers and tracking cookies before consent and after a reject, and the Global Privacy Control response.

What's Inside

• What it does
• Quick start
• Prerequisites
• Example prompts
• Tool
• Inputs
• Pricing
• Your keys
• Full actor documentation
• License

What it does

Audit one or more websites for cookie consent behavior from an EU address. Each domain is loaded in fresh browser sessions: once before any consent click, once after clicking the reject control on the first layer of the banner, and once with Global Privacy Control on. Returns one row per domain: the consent management platform found (TCF __tcfapi, OneTrust, Cookiebot, Usercentrics, Didomi, and others), whether accept and reject controls sit on the first layer, tracking cookies and requests to known tracker hosts before consent and after the reject, Google Consent Mode denied pings, the GPC comparison and /.well-known/gpc.json, a list of signals, and the version of the fixed tracker list used. Signals for review, not legal findings. Cookie values are never returned. A run that does not succeed is returned as an error with its run ID. Read-only on the audited sites; requires an APIFY_TOKEN and consumes Apify credits per audited domain.

All of the work runs on Apify. This package is a thin client that starts the actor run, waits for it, and hands back the dataset rows.

Quick start

You need Node.js 18 or newer and an Apify account with an API token.

Add this to your Claude Desktop config (claude_desktop_config.json), Cursor, or any MCP client:

{
  "mcpServers": {
    "mamba-cookie-consent-audit": {
      "command": "npx",
      "args": [
        "-y",
        "@mambalabsdev/mcp-cookie-consent-audit"
      ],
      "env": {
        "APIFY_TOKEN": "your-apify-token"
      }
    }
  }
}

Restart the client. The audit_cookie_consent tool appears.

Prerequisites

• Node.js 18 or newer.
• An Apify API token from console.apify.com/account/integrations, set as APIFY_TOKEN. The server lists its tool without a token; a call needs one.

Example prompts

• "Audit example.de for cookie consent from Germany and tell me what fires before consent."
• "Check these five client sites from France: is there a reject button on the first layer, and does anything still track after a reject?"

Tool

audit_cookie_consent. One tool. Example arguments:

{
  "domains": ["example.de", "example.fr"],
  "proxy_country": "DE"
}

Inputs

Every buyer facing input of the actor, unchanged. Omitted inputs take the actor's own defaults.

Pricing

Pay per event on Apify, billed to your Apify account. Prices in USD.

Blocked, timed out, partial, cached, and invalid rows are never charged.

Your keys

The actor needs no provider key. It loads public pages with the page and its banner deciding requests sent through the Apify proxy, and holds no key of its own.

Full actor documentation

apify.com/mambalabs/cookie-consent-audit

License

MIT. See LICENSE.