com.mambabuilt/mcp-cookie-consent-audit
NPM · @MAMBALABSDEV/MCP-COOKIE-CONSENT-AUDIT
Audit a site's cookie consent from the EU: trackers before consent, reject, after reject, GPC.
Available components
Last scanned (7 hours ago)
Scores higher than 40% of npm servers
Category Web Scraping
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 3 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability64
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 407 tokens (~407/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Oct 26 +11
- Known CVEs: unverified → pass ▲ security
- Dependency health: unverified → 0.85 ▲ functional
- 19 Oct 26 58
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 23 Oct 2026 · Analysed npm/@mambalabsdev/mcp-cookie-consent-audit@1.0.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
audit_cookie_consent Audit cookie consent ~407
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.
| Name | Type | Req | Description |
|---|---|---|---|
| check_gpc | string | – | Load 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. |
| domain | string | – | The website to audit, for example example.de or https://www.example.de/. The homepage is audited. Give domain or domains. |
| domains | array | – | More domains or URLs to audit in the same run. Duplicates are skipped. Up to 500 per run. |
| max_charge_usd | string | – | Optional. Stop the run before the audit charges would pass this amount. |
| proxy_country | string | – | The 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. |
| skip_cache | string | – | A domain audited in the last 24 hours with the same settings is returned from cache at no charge. true audits it again. Default false. |
No output schema declared.
No examples provided.
How do I install the com.mambabuilt/mcp-cookie-consent-audit server?
com.mambabuilt/mcp-cookie-consent-audit runs locally as an npm package, launched with npx -y @mambalabsdev/mcp-cookie-consent-audit. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @mambalabsdev/mcp-cookie-consent-audit
claude mcp add com-mambabuilt-mcp-cookie-consent-audit -- npx -y @mambalabsdev/mcp-cookie-consent-audit
What is the com.mambabuilt/mcp-cookie-consent-audit server?
com.mambabuilt/mcp-cookie-consent-audit is listed in the public MCP registry as com.mambabuilt/mcp-cookie-consent-audit. Audit a site's cookie consent from the EU: trackers before consent, reject, after reject, GPC. This page covers its npm package (@mambalabsdev/mcp-cookie-consent-audit).
Is the com.mambabuilt/mcp-cookie-consent-audit server safe to use?
com.mambabuilt/mcp-cookie-consent-audit scores 70 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 23 October 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the com.mambabuilt/mcp-cookie-consent-audit server expose?
com.mambabuilt/mcp-cookie-consent-audit exposes 1 tool: audit_cookie_consent. Their descriptions and schemas cost roughly 407 tokens of context every time the server is loaded.
Is the com.mambabuilt/mcp-cookie-consent-audit server still maintained?
com.mambabuilt/mcp-cookie-consent-audit is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the com.mambabuilt/mcp-cookie-consent-audit server under?
com.mambabuilt/mcp-cookie-consent-audit declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.