com.cookieinspector/cookieinspector

Est-ce que com.cookieinspector/cookieinspector est sûr ?

Au dernier audit MCP Hub, le serveur MCP « com.cookieinspector/cookieinspector » 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 9 outils

• explain_finding≈ 169 tokens

  Explain a CookieInspector finding code (e.g. THIRD_PARTY_PRE_CONSENT) or what to check in a named consent platform (e.g. Cookiebot). No network call. Technical findings, not legal advice.

  Paramètres, retour & exemple (1)

  Paramètres

  • code · string · requis
    A finding code from a report, such as COOKIES_BEFORE_CONSENT, or a consent platform name such as OneTrust

  Exemple d'appel

  {"name": "explain_finding", "arguments": {"code": "texte"}}

  Exemple de retour

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

• get_capabilities≈ 161 tokens

  Describe what CookieInspector checks on a website (cookies and trackers before and after the consent click, banner behaviour, consent platform, Google Consent Mode), which tools work without an account, which need a CookieInspector API key, and the quotas. Call this first when unsure which tool to use. Technical findings, not legal advice.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "get_capabilities", "arguments": {}}

  Exemple de retour

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

• get_prescan_result≈ 213 tokens

  Return the result of a pre-scan started with prescan_site: riskScore (0 best, 100 worst, the same scale as the full report), risk level, how many cookies load before consent, up to five trackers by name, the consent platform and its confidence, Google Consent Mode status, three findings, and the report link. This is a header-and-HTML pre-scan, single page; the full scan with a real browser, evidence and fix guide requires a CookieInspector account. Technical findings, not legal advice.

  Paramètres, retour & exemple (1)

  Paramètres

  • preScanId · string · requis
    The preScanId returned by prescan_site

  Exemple d'appel

  {"name": "get_prescan_result", "arguments": {"preScanId": "texte"}}

  Exemple de retour

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

• get_scan_findings≈ 140 tokens

  The findings of a scan on the connected account, with severity, the affected resource and the recommendation, up to 25. Use explain_finding for what a code means. Technical findings, not legal advice.

  Paramètres, retour & exemple (1)

  Paramètres

  • scanId · string · requis
    The scanId returned by start_scan or list_scans

  Exemple d'appel

  {"name": "get_scan_findings", "arguments": {"scanId": "texte"}}

  Exemple de retour

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

• get_scan_status≈ 130 tokens

  Status of a scan on the connected account: queued, running, completed or failed, with the riskScore (0 best, 100 worst) once done. Technical findings, not legal advice.

  Paramètres, retour & exemple (1)

  Paramètres

  • scanId · string · requis
    The scanId returned by start_scan or list_scans

  Exemple d'appel

  {"name": "get_scan_status", "arguments": {"scanId": "texte"}}

  Exemple de retour

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

• get_scan_summary≈ 145 tokens

  Summary of a completed scan on the connected account: risk score (0 best, 100 worst), verdict, banner and consent platform, cookie and tracker counts, the top issues and the report link. Technical findings, not legal advice.

  Paramètres, retour & exemple (1)

  Paramètres

  • scanId · string · requis
    The scanId returned by start_scan or list_scans

  Exemple d'appel

  {"name": "get_scan_summary", "arguments": {"scanId": "texte"}}

  Exemple de retour

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

• list_scans≈ 128 tokens

  The most recent scans on the connected account, newest first (up to 20), each with its riskScore (0 best, 100 worst). Technical findings, not legal advice.

  Paramètres, retour & exemple (1)

  Paramètres

  • limit · integer|null · optionnel
    How many to return, 1 to 20. Default 10.

  Exemple d'appel

  {"name": "list_scans", "arguments": {"limit": 1}}

  Exemple de retour

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

• prescan_site≈ 184 tokens

  Start a quick, anonymous pre-scan of a public website's home page: HTTP headers and HTML only, no real browser. Returns a preScanId to pass to get_prescan_result and a link to the report on cookieinspector.com. CookieInspector works alongside any consent platform; it checks what the banner actually does. Technical findings, not legal advice.

  Paramètres, retour & exemple (1)

  Paramètres

  • url · string · requis
    The website to check, e.g. example.com or https://example.com

  Exemple d'appel

  {"name": "prescan_site", "arguments": {"url": "texte"}}

  Exemple de retour

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

• start_scan≈ 242 tokens

  Start a full CookieInspector scan with a real browser (before and after the consent click, up to 5 pages) on the connected account. Optional region: main (US East), us-west, eu-de (Germany, for EU-targeted banners). Uses the plan's monthly scans. Returns a scanId to poll with get_scan_status, then get_scan_summary. Technical findings, not legal advice.

  Paramètres, retour & exemple (3)

  Paramètres

  • url · string · requis
    The website to scan, absolute, e.g. https://example.com
  • region · string|null · optionnel
    Scan location: main, us-west or eu-de
  • evaluateCcpa · boolean|null · optionnel
    Also evaluate CCPA/CPRA (California). Default true.

  Exemple d'appel

  {"name": "start_scan", "arguments": {"url": "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://api.cookieinspector.com/mcp