Mcp Cookie Consent Audit

com.mambabuiltPublished by mambabuilt.comv1.0.2Updated Nov 7, 2026

Audit a site's cookie consent from the EU: trackers before consent, reject, after reject, GPC.

The publisher's own server: audit.domains - Domain Valuation

Overview

AI-generated overview

Audits websites' cookie consent from an EU vantage point via an Apify actor, reporting trackers before consent, after reject, and under GPC.

What you can do
  • Audit one or many domains for cookie consent behavior from an EU address, with up to 500 domains per run and a choice of EU proxy country.
  • Get one row per domain covering the consent platform detected, whether accept and reject controls appear on the first banner layer, tracking cookies and tracker requests before consent and after a reject, Google Consent Mode denied pings, and the Global Privacy Control comparison.
  • Compare sessions run before any click, after clicking reject, and with GPC enabled, and receive a list of signals plus the tracker-list version used.
When to use it
Useful for privacy, compliance or marketing reviews that need to check whether client or competitor sites set trackers before consent, offer a first-layer reject, or honor Global Privacy Control. Suited to batch checks of several sites from a specific EU country.
Requirements
Runs locally as an npm package over stdio, so Node.js 18 or newer is needed. An Apify account and an Apify API token supplied as the APIFY_TOKEN environment variable are required for calls; the tool is listed without one. All work runs on Apify, so network access is needed.
Before you install
Each audited domain consumes Apify credits billed to your Apify account (per-domain and per-run-start events), so costs scale with the number of domains; an optional max_charge_usd input can cap a run. The APIFY_TOKEN is a secret and should be kept out of shared configs. Results are review signals, not legal findings, and cached results are reused unless skip_cache is set.

Installation

In SourceWeft

  1. Open Mcp Cookie Consent Audit in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Cookie Consent Audit MCP Server

[Glama score] [MCP Registry] [npm version] [npm downloads] [license] [mcpservers.org]

[Cookie Consent Audit MCP server]

An MCP server for the Mamba Labs GDPR Cookie Banner and Consent Checker 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

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:

json
{  "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

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:

json
{  "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.

InputTypeRequiredDescription
domainstringnoThe website to audit, for example example.de or https://www.example.de/. The homepage is audited. Give domain or domains.
domainsarraynoMore domains or URLs to audit in the same run. Duplicates are skipped. Up to 500 per run.
proxy_countrystringnoThe EU country the browser connects from: DE, FR, NL, IE, IT, ES, SE, PL, AT, BE, DK, FI, or none. Default DE. none is not an EU vantage point.
check_gpcstringnoAlso run the Global Privacy Control session and read /.well-known/gpc.json. Default true.
max_charge_usdstringnoOptional. Stop the run before the audit charges would pass this amount.
skip_cachestringnoA domain audited in the last 24 hours with the same settings comes back from cache at no charge. true audits it again. Default false.

Pricing

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

EventFree planBronzeSilverGold
domain-audited, per fully audited domain$0.05$0.0475$0.045$0.0425
apify-actor-start, per run start$0.001$0.001$0.001$0.001

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.

Source: README.md at commit e936a45

Tools

1

Version history

2
  1. v1.0.2LatestNov 5, 2026
  2. v1.0.1Oct 19, 2026

Score

90% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts
  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Audit integrations