MCP.Market

Cookie Consent Audit MCP server

by mambabuilt.com·com.mambabuilt/mcp-cookie-consent-audit·v1.0.1

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

B77/100grade B
What users say
No reviews yet
Be the first
Safety scan
B77/100

full report

Adoption
Growing

0 stars107 downloads/wk

Reviews

Write one

Nobody has reviewed Cookie Consent Audit yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Cookie Consent Audit tools (1)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • audit_cookie_consent

Public scan report

scanner v0.1.10 · 2026-10-27 · same rubric, same numbers if you re-run it

no findings
  • Code scan2 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancelast push 7 days ago15/15
  • Maintainer identitynamespace and repository owner differ4/10
Overall 77/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Cookie Consent Audit compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
77/100
higher than 50% of 48,255 servers
Tools
1
the typical server has 7
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
Downloads a week
107
more than 64% of 12,191 servers with a package

What its tools let an agent do: 1 read

Install Cookie Consent Audit in Claude Code, Cursor or VS Code

Runs npx -y @mambalabsdev/mcp-cookie-consent-audit on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add mcp-cookie-consent-audit -- npx -y @mambalabsdev/mcp-cookie-consent-audit
Add to Cursor

What the publisher says

From the Cookie Consent Audit repository's README, as published. We do not edit it. Read it on GitHub

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 APIFYTOKEN 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 (claudedesktopconfig.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 auditcookieconsent tool appears.

Prerequisites

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Cookie Consent Audit: common questions

Is Cookie Consent Audit MCP server safe?
Mostly: it is graded B (77/100). Read the Cookie Consent Audit safety report
How do I install Cookie Consent Audit?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Cookie Consent Audit need an API key?
Yes. The registry entry asks for APIFY_TOKEN.
Is Cookie Consent Audit maintained?
The last commit was 15 days ago (2026-10-20). The latest release is v1.0.1.
How does Cookie Consent Audit compare with other MCP servers?
safety score 77/100 (higher than 50% of 48,255 servers); tools 1 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

More from mambabuilt.com →