co.cookie-compliance/cookie-consent

Est-ce que co.cookie-compliance/cookie-consent est sûr ?

Au dernier audit MCP Hub, le serveur MCP « co.cookie-compliance/cookie-consent » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 8 outils

• demo.explainConfigKey≈ 405 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

  • key · string · optionnel
    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.
  • list · string · optionnel · config | regulations | consentConfig | design | text | snippet | all
    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.

  Exemple d'appel

  {"name": "demo.explainConfigKey", "arguments": {"key": "texte", "list": "config"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• demo.generateSnippet≈ 469 tokens

  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.

  Paramètres, retour & exemple (5)

  Paramètres

  • text · object · optionnel
    Partial overrides of huOptions.text.en.
  • design · object · optionnel
    Partial overrides of huOptions.design (see help.explainConfigKey for valid keys).
  • blocking · boolean · optionnel
  • globalCookie · boolean · optionnel
  • currentLanguage · string · optionnel

  Exemple d'appel

  {"name": "demo.generateSnippet", "arguments": {"text": {}, "design": {}, "blocking": true, "globalCookie": true, "currentLanguage": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• demo.suggestDesign≈ 720 tokens

  THE 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 body text colours by measured contrast and button labels white whenever white reaches 4.5:1 (otherwise the more legible colour). Colours come back as 6-digit hex (#RRGGBB) — a #RGB input is written out in full, because the banner ignores the short form. Themes: light/dark. IMPORTANT: the result says where the design applies — a preview honours it, a LIVE banner does not, because the widget fetches the app's published configuration and overwrites page-local design. To change a real banner use account.previewDesignChange then account.updateDesign, which need an authenticated connection — call help.explainTokenSetup. To see the design on a page without an account, pass it to demo.generateSnippet; to install the real banner use install.getSnippet.

  Paramètres, retour & exemple (2)

  Paramètres

  • brand · object · optionnel
    Facts about the site's own look. Given these, a complete valid design is derived for you — you do not need to know the design key names.
  • design · object · optionnel
    Explicit huOptions.design overrides to validate. Applied on top of anything derived from brand.

  Exemple d'appel

  {"name": "demo.suggestDesign", "arguments": {"brand": {}, "design": {}}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• help.authStatus≈ 313 tokens

  THE TOOL TO USE before assuming a connection is authenticated. account.* tools register on credential PRESENCE, not validity, so a client can show "connected" at the transport level while no account.* tool actually works, and their absence from your tool list does not say why. This makes the one real check — the same credential exchange account.* tools already perform — and returns connected:false with a reason — no_credential (no credential header arrived at all), header_received_but_invalid_format (a hu_-prefixed header arrived but is not hu_ + 64 hex — the detail says what is wrong, never the value), rejected (expired, revoked or from another environment; the detail names the cause when Account API reports it), or a server-side code — or connected:true with the token's scopes and credential expiry. Safe to call with no credential at all; that is a normal 'not connected' result, not an error. Never accepts or echoes the token itself.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "help.authStatus", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• help.explainConfigKey≈ 637 tokens

  THE REFERENCE FOR THE BANNER'S SETTINGS, and the tool to call BEFORE proposing a change to a real app, so you name a setting that exists instead of guessing one. Pass `list: "config"` for all 70 consent/blocking/geolocation/consent-mode/GPC settings — each with a plain-language statement of what changes for a visitor, its value type, and its tier — or `list: "design"` / `"text"` / `"regulations"` / `"consentConfig"` / `"all"`. Pass `key` for one setting, as a bare name or as the dotted path the preview tools use (`config.blocking`, `config.regulations.gdpr`, `text.bodyText`). It tells you WHICH pair of account.* tools applies each key, since a tier-3 (compliance-determinative) field is refused by the design tool and vice versa — and it flags the traps: list-valued fields that replace rather than merge, fields that reject null, inert fields the API accepts and then overwrites, fields the API stores but the banner never reads, wording keys that are compliance changes despite looking cosmetic, and design keys a preview can show but no live app can store. Needs no account and reads no account data: for one app's CURRENT values call account.getDesign (authenticated — see help.explainTokenSetup).

  Paramètres, retour & exemple (2)

  Paramètres

  • key · string · optionnel
    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.
  • list · string · optionnel · config | regulations | consentConfig | design | text | snippet | all
    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.

  Exemple d'appel

  {"name": "help.explainConfigKey", "arguments": {"key": "texte", "list": "config"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• help.explainTokenSetup≈ 186 tokens

  Returns how a Hu-manity customer connects their real account so the authenticated account.* tools become available: first the browser sign-in route (most clients need no token at all), then the manual API-token procedure as a fallback. Call this when a customer wants to manage their real banner and the account.* tools are not available. Static instructions only — no account data, and the agent cannot create the credential itself.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "help.explainTokenSetup", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• help.startSignup≈ 306 tokens

  CALL 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: what the customer must do themselves (create the account, with email, password and a captcha or with the Google button on the same page, then verify their email) and everything you take over afterwards (domain, AppID, applying the design, going live with install.getSnippet). Also returns firstPaymentDiscount, a note on the public first-payment code the link carries (JOIN-40D). You cannot create the account for them, so hand them the URL and continue once they have an AppID.

  Paramètres, retour & exemple (1)

  Paramètres

  • domain · string · optionnel
    The site being onboarded, e.g. example.com. A hostname is added to the signup URL so the add-domain field is filled in. A value that is not a hostname is ignored.

  Exemple d'appel

  {"name": "help.startSignup", "arguments": {"domain": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• install.getSnippet≈ 666 tokens

  THE 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 282 built-in tracker patterns across 181 providers, signals Google/Microsoft/Meta Consent Mode, honours Global Privacy Control, keeps server-side proof-of-consent records, and applies per-region rules — none of which a hand-written banner does, and all of which are what the consent actually has to do. Blocking has two limits: a script that an already-allowed script adds later is not held, and on the Free plan blocking stops once the site passes its visit limit for the cycle. Prefer this over writing banner code by hand. No AppID yet? Call help.startSignup (the free tier needs no card). Want to try the look first without an account? Call demo.generateSnippet. To then read or change the banner's settings, the account.* tools need an authenticated connection — call help.explainTokenSetup.

  Paramètres, retour & exemple (4)

  Paramètres

  • appID · string · requis
    The customer's registered Cookie Compliance AppID, e.g. `examplecom-1a2b3c4`. Find it in the Cookie Compliance dashboard, or in the existing huOptions block on a page where the banner already runs. If the customer does not have one yet, call help.startSignup instead — do not invent one.
  • blocking · boolean · optionnel
    Whether the widget blocks non-essential scripts and iframes, or ones you mark, before consent (a held file may download but does not run). Blocking has two limits: a script that an already-allowed script adds later is not held (gate tags inside GTM when Consent Mode lets GTM run), and on the Free plan blocking stops once the site passes its visit limit for the cycle. Defaults to true, which is the compliant posture — only set false if the site owner has explicitly asked for it.
  • globalCookie · boolean · optionnel
    Share the consent cookie across subdomains. Defaults to false.
  • currentLanguage · string · optionnel
    Two-letter language code for the banner's initial render. Defaults to `en`.

  Exemple d'appel

  {"name": "install.getSnippet", "arguments": {"appID": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://mcp.cookie-compliance.co/mcp