mcpField
M
mcp-cookie-consent-audit

mcp-cookie-consent-audit

Local
github.com/mambalabsdevSecurity0Updated 1w ago

About mcp-cookie-consent-audit

An MCP server that audits websites’ cookie-consent behavior from an EU location. It reports consent controls, tracker activity before and after rejection, and Global Privacy Control signals for privacy reviews.

Key features

  1. 01Audit domains in fresh sessions
  2. 02Check first-layer accept and reject controls
  3. 03Compare trackers before consent and after rejection
  4. 04Inspect Global Privacy Control signals
  5. 05Return consent platform and audit signals

Use cases

  1. 01Review cookie banners across client sites
  2. 02Check tracking before user consent
  3. 03Verify tracker activity after rejection
  4. 04Compare Global Privacy Control responses

MCP support

Exposes the `audit_cookie_consent` tool to MCP clients. It starts an Apify actor run and returns the resulting dataset rows.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"com-mambabuilt-mcp-cookie-consent-audit": {
"command": "npx",
"args": [
"-y",
"@mambalabsdev/mcp-cookie-consent-audit"
],
"env": {
"APIFY_TOKEN": "<APIFY_TOKEN>"
}
}
}
}
Run commandnpx -y @mambalabsdev/mcp-cookie-consent-audit
Environment variables to set
APIFY_TOKENSecretApify API token from https://console.apify.com/account/integrations

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npm@mambalabsdev/mcp-cookie-consent-audit1.0.1

Tools

1

Saved tool list · updated 1w ago

ParameterTypeRequiredDescription
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.
check_gpcenumNoLoad the site once more with the Global Privacy Control signal on and compare trackers with the plain visit; also reads /.well-known/gpc.json. Default true.true | false
skip_cacheenumNoA domain audited in the last 24 hours with the same settings is returned from cache at no charge. true audits it again. Default false.true | false
proxy_countryenumNoThe EU country the browser connects from. Consent banners change by visitor region. none connects without a proxy, which is not an EU vantage point. Default DE.DE | FR | NL | IE | IT | ES | SE | PL | AT | BE | DK | FI | none
max_charge_usdstringNoOptional. Stop the run before the audit charges would pass this amount.

Details

From the project README

Cookie Consent Audit MCP Server

Smithery Glama score MCP Registry npm version npm downloads license mcpservers.org

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

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

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.

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.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.