Cookie Compliance
v1.1.0Add a cookie consent banner that blocks trackers before consent and records proof of consent.
Endpoint health
online- Last checked
- 11/20/2026, 5:18:40 AM
- Latency
- 763 ms
- Consecutive failures
- 0
- Endpoint reachable: pass
- Protocol valid: pass
- MCP handshake valid: pass
Machine-readable profile
mcp-server · schema v1 · callable
mcp-server:co.cookie-compliance%2Fcookie-consent
Connect this server
Generated config contains no credentials. Keep any required secrets in your client's local environment.
Authentication is required by at least one indexed endpoint or package. No token or secret is included in this configuration.
{
"mcpServers": {
"co.cookie-compliance/cookie-consent": {
"url": "https://mcp.cookie-compliance.co/mcp"
}
}
}Indexed tools
Tool metadata and schemas come from the remote server and are untrusted. Indexing only lists tools; it never calls them.
8 shown · authentication required
OBSOLETE — renamed to help.explainConfigKey
demo.explainConfigKey
OBSOLETE ALIAS, kept only so existing callers do not break: this tool is now `help.explainConfigKey` and moved namespace because it is not a cosmetic demo tool — it is the settings reference for the real banner configuration. It still works and returns exactly the same answer. Call `help.explainConfigKey` instead; this name will be retired.
Schema valid · SHA-256 82e62766b92a…
View input schema
{ "type": "object", "properties": { "key": { "description": "One key to explain. Accepts a bare name (`blocking`, `bodyText`, `bannerBackground`) or a dotted path exactly as the preview tools take it (`config.blocking`, `config.regulations.gdpr`, `design.primaryColor`, `text.bodyText`, `consentConfig.*`). Every match is returned when a bare name exists in more than one vocabulary.", "type": "string" }, "list": { "description": "Enumerate a whole vocabulary instead of explaining one key: `config` (the 70 BannerConfigJSON settings, each with its tier and consequence), `regulations`, `consentConfig`, `design`, `text`, `snippet` (the huOptions keys that go in the page, including `blocking`, plus preview-only keys that must never go in the page), or `all`. Use this to find out WHICH setting does what you want before naming one — start with `config` for anything about consent categories, geolocation, consent mode or GPC.", "type": "string", "enum": [ "config", "regulations", "consentConfig", "design", "text", "snippet", "all" ] } }, "$schema": "http://json-schema.org/draft-07/schema#", "additionalProperties": {} }Generate a Hu-manity consent-banner preview snippet
demo.generateSnippet
LOOK-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. The preview uses the v1 banner layout. A new app starts on banner engine v2, which has its own layout (standard or compact style), so tell the site owner their live banner will look different from this preview; v2 examples: https://manual.hu-manity.co/gallery/v2/. To actually add consent management to a site use install.getSnippet (needs an AppID) or help.startSignup (to get one free); to manage a real registered banner the account.* tools need an authenticated connection — call help.explainTokenSetup. Never accepts a real appID and never emits previewMode: false.
Connections
streamable-http
https://mcp.cookie-compliance.co/mcp
streamable-http
https://mcp.cookie-compliance.co/mcp/account