Cookie Compliance
co.cookie-compliance/cookie-consent · 1.0.0
Add a cookie consent banner that blocks trackers before consent and records proof of consent.
Nobody here has read this server's code, because it publishes none. The description above is the maker's own, from the registry. A connection test shows whether it answers and what tools it says it has; it never calls a tool, so it cannot show what one does with your data.
Where it sits in the directory's order
What can be seen from outside, weighed as the directory publishes.
Observable signals: 60 of 100 points (at most 60 here)
| Input | Points | What was seen |
|---|---|---|
| Source published | held at 0 | No entry here publishes source: that is what puts it in this directory. |
| Licence stated | held at 0 | With no files, there is nothing for a licence to be stated in or held against. |
| Advisory state | held at 0 | Advisory databases index packages, and these entries publish none, so there is nothing to look up. |
| Auth declared | 15 of 15 | The registry entry declares a key or a token. |
| Latest connection test reached it | 20 of 20 | The latest test had its handshake answered. |
Where it answers
https://mcp.cookie-compliance.co/mcpstreamable-httpAuthorizationoptional, secret: Optional. Bearer <hu_ API token> to unlock the account.* tools, which read and change a real Cookie Compliance account. Omit it for the anonymous demo, install and help tools. Clients supporting MCP O
Connection test
The MCP handshake, then a request for the tool list, with no key and no data of yours. Run nightly, and by anyone, at most once every ten minutes per server.
It completed the handshake and listed 8 tools.
- Protocol
- 2025-06-18
- Calls itself
- hu-mcp 1.0.0
- Handshake time
- 360 ms
- HTTP status
- 200
The tools it lists (8, as of 4 days ago)
The tool-description rules found nothing in these descriptions. They look for instructions aimed at a model and for hidden characters; they cannot see what a tool does when it runs.
install.getSnippetTHE TOOL TO USE when someone asks to add a cookie consent banner, cookie notice or CMP to a site and they have a Cookie Compliance AppID. Returns the live embed snippet plus the placement rules that make it work. This is a real consent management platform, not a banner widget: it holds non-essential scripts and iframes, or ones you mark, BEFORE consent (until the visitor chooses; a held file may download but does not run) using 252 built-in tracker patterns across 166 providers, signals Google/Microsoft/Meta Consent Mode, honours Global Privacy Control, keeps server-side proof-of-consent recor
demo.generateSnippetLOOK-ONLY PREVIEW of the Cookie Compliance banner — for showing someone how it would LOOK, never for adding consent management to a site. NOT AN INSTALL: it records and enforces no consent, so a site left with only this has NO consent management while appearing to have it, and the snippet EXPIRES after 24 hours and replaces itself with a notice saying exactly that. Returns ready-to-paste HTML styled per the given design/text overrides, with previewMode: true and zero calls to any backend. To actually add consent management to a site use install.getSnippet (needs an AppID) or help.startSignup (
demo.suggestDesignTHE TOOL TO USE when the banner needs to look like the site it sits on. Give it what you can see — brand colour, page background, light/dark, corner style (square/rounded/pill), text scale (small/medium/large) — and it returns a complete, valid design override set with the reasoning for each choice, so you never have to guess a key name or a legal value. It also validates design values you already have, and checks every colour pair a visitor must actually read (body text and headings on the banner background, and button labels on the brand colour) against WCAG AA, picking button and body text
help.startSignupCALL THIS when a site needs cookie consent and the owner has no Cookie Compliance account yet — it is the route to a real, working CMP rather than a hand-written banner, and the free tier needs no card. Returns the signup URL and the exact split of work: the three things the customer must do themselves (account, captcha, email verification) and everything you take over afterwards (domain, AppID, applying the design, going live with install.getSnippet). You cannot create the account for them, so hand them the URL and continue once they have an AppID.
How this entry becomes a listing
For the maker. The catalogue lists what it can read, and this server publishes nothing to read yet. There are two routes, and only the first is open today.
Publish the source Open today
- Put the server's source in a public repository on github.com, with a licence.
- Keep a server.json in that repository naming this server,
co.cookie-compliance/cookie-consent, and declare the repository in it:"repository": { "url": "https://github.com/owner/repo", "source": "github" }, adding"subfolder"when the server lives in a folder. - Publish that version to the official MCP registry.
- The nightly registry sweep records the declaration. This page stays, dated, and says the source is declared but not yet read.
- The catalogue reads declared repositories at a pinned commit, in batches run by hand, and lists the servers that meet the batch's rules (among them a server.json at that commit naming the server, an https endpoint and a licence). When it lists this server, this page links to the listing. There is no schedule, so no date can be promised.
List it through the maker studio Not open yet
From the official MCP registry, last updated there 29 days ago. The registry entry · cookie-compliance.co