Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

CookiePal

REMOTE · MCP.COOKIEPAL.IO

Manage your CookiePal cookie banner: domains, the banner tag and style, and cookie scan reports.

Available components

+3 this week 70 Trust /100

Last scanned (22 hours ago)

Scores higher than 55% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Security

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security57
Transport & Reachability100
Schema Quality & AI Usability69
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 2929 tokens (~172/item across 17 items; 17 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 Management57
  • Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage91
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 70% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 17 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
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 19 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Nov 26 0
    • Tool “customise_banner” rewrote its description, which is the text the model reads security
    • “customise_banner” reworded the description of “logo” cosmetic
  • 17 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Nov 26 0
    • Tool “upload_scan_report” rewrote its description, which is the text the model reads security
    • Tool “regenerate_banner” is now declared destructive security
    • Tool “set_banner_mode” is now declared destructive security
    • “plan_check” reworded the description of “url” cosmetic
  • 11 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

  • 9 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

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 21 Nov 2026 · Probed https://mcp.cookiepal.io/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=cookiepal.io CN=Amazon RSA 2048 M01,O=Amazon,C=US 14 Jan 2026 12 Feb 2027 RSA 2048 SHA256-RSA 2483313e0147801b9602ac59276974b
SANs: cookiepal.io, *.cookiepal.io
CN=Amazon RSA 2048 M01,O=Amazon,C=US (CA) CN=Amazon Root CA 1,O=Amazon,C=US 23 Aug 2022 23 Aug 2030 RSA 2048 SHA256-RSA 77312380b9d6688a33b1ed9bf9ccda68e0e0f
CN=Amazon Root CA 1,O=Amazon,C=US (CA) CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US 25 May 2015 31 Dec 2037 RSA 2048 SHA256-RSA 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.cookiepal.io. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
io. DS published 38690 8 Verified
cookiepal.io. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.cookiepal.io/mcp Verified 200
http (plaintext) http://mcp.cookiepal.io/mcp HTTPS enforced
MCP tools · 17 exposed · ~2,929 tokens

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 →

Tool Tokens
add_domain ~146

Adds a website domain to the connected CookiePal account on the free plan, with the same checks as the CookiePal dashboard, and queues its banner build. Nothing is scanned on CookiePal’s side: the result says how to run the first scan on the user’s computer. An organisation can add at most 10 domains a day this way. Other tools keep using the default domain unless given the new one.

NameTypeReqDescription
domainstringyesThe domain to add, such as example.com. A URL is accepted: its scheme, a leading www. and any path are dropped. A port is refused, as in the dashboard, so send example.com, not example.com:8080.
NameTypeReqDescription
addedTodaynumberyesDomains this organisation has added through the MCP server today, this one included.
bannerBuildQueuedbooleanyes–
dailyLimitnumberyes–
domainIdstringyes–
nextStepstringyes–
planstringyes–
urlstringyes–

No examples provided.

check_gcm_status ~245

Reads Google Consent Mode on one of your CookiePal domains, from a page load on the user’s own computer, names the problem if there is one, and records the result on the domain as a local reading. Run this again any time to re-check. The local run this needs is made only by the CookiePal plugin in a coding agent on the user’s own computer: Claude Code, Codex or Cursor. claude.ai, Claude Code on the web and other cloud agents run in the cloud, so they cannot make it, and a crawler or browser run anywhere else does not stand in for it. The result reports what was found. It does not assess whether a site, page or banner complies with any law, so it is never a verdict of compliant or non-compliant.

NameTypeReqDescription
domainIdstring–Which domain was checked. Omit it for the account’s default domain.
readingobjectyesExactly what the gcm check command returned; never hand-built.
seenAtstringyesWhen the reading was taken, ISO 8601.
urlstringyesThe page that was read on the user’s computer.
NameTypeReqDescription
checkedAtstringyes–
domainIdstringyes–
entriesMissingDefaultarrayyes–
evidencestringyes–
fixstringyes–
nextStepstringyes–
problemstringyes–
statusstringyes–
titlestringyes–
urlstringyes–

No examples provided.

classify_cookies ~89

Sets the category for a list of cookies on one of your CookiePal domains, and reports the result for each one. Send the category from @cookiepal-oss/cookie-db (necessary, functional, analytics, performance, advertisement or other).

NameTypeReqDescription
cookiesarrayyes–
domainIdstring–Which domain these cookies belong to. Omit it for the account’s default domain.
NameTypeReqDescription
domainIdstringyes–
resultsarrayyes–

No examples provided.

connect_account ~185

Connects this client to a CookiePal account, opening sign-in (or sign-up, for someone without an account) in the browser if needed, then reports who is connected: the user, the organisation and the domain other tools act on by default. Pass the plugin’s install ID only with linkInstall: true if the user agreed to link it to this account, or linkInstall: false if they said no.

NameTypeReqDescription
installIdstring–The plugin’s install ID, sent with `linkInstall` to carry out the user’s answer to linking it to this account. Leave it out when the user shared no install ID.
linkInstallboolean–Required with `installId`: true only if the user agreed to link the install ID to this account (a separate question from sharing it), false if they said no, which also removes any link made before.
NameTypeReqDescription
domainobjectyes–
emailstringyes–
installLinkedbooleanyesWhether the install ID is linked to this account now, after this call.
installUnlinkedbooleanyes–
organisationIdstringyes–
organisationNamestring––
userIdstringyes–

No examples provided.

customise_banner ~247

Changes how one of your CookiePal domains’ banner looks and reads: its colours, logo type (default only), positions, and the title, description and button texts per language. Give only what you want to change; everything else keeps its saved value. It does not upload a custom logo or change category texts; use the CookiePal dashboard for those. Colour, logo and position changes queue a rebuild (skipped, and said so, if the domain has reached its page-view limit); texts go live without one.

NameTypeReqDescription
colorsobject–Only the colours you give change; the rest keep their saved value.
domainIdstring–Which domain to customise. Omit it for the account’s default domain.
logoobject–The banner’s logo: set type default to use CookiePal’s default logo (it has a fixed colour). A custom logo is kept as it is unless you set a type.
positionsobject–Only the positions you give change; the rest keep their saved value.
textsarray–Banner and preference-centre copy per language the banner already has, as plain text; paragraphs are separated by a blank line.
NameTypeReqDescription
bannerEnabledbooleanyes–
domainIdstringyes–
messagestringyes–
rebuildstringyes–
saved–yes–
textsarrayyes–

No examples provided.

forget_install ~132

Deletes the checks CookiePal stored under one install ID. Run it from the plugin before the ID is removed from the machine, because once the ID is gone there is nothing left to look the checks up by. It answers with how many were deleted and how many remain: only a run reporting no remainder has finished, and running it again deletes just what is left. An ID that stored nothing reports zero of both. It also unlinks the ID from any CookiePal account it was connected to. No account needed.

NameTypeReqDescription
installIdstringyesThe install ID to erase. Every check stored under it is deleted.
NameTypeReqDescription
deletedintegeryesHow many stored checks were deleted. Zero is a normal answer.
remainingintegeryesStored checks that could not be deleted this time. Normally zero; when it is not, keep the install ID and run this again, which deletes only what is left.
unlinkedbooleanyesWhether the install ID was linked to a CookiePal account, and that link removed.

No examples provided.

get_install_snippet ~134

Returns the CookiePal banner script tag to paste into a site, for one domain in the connected account. It is byte-for-byte the tag the CookiePal dashboard copies for that domain, including `defer` for a Shopify store. Paste it as given: the URL it loads is specific to the domain, and a tag built by hand or copied from another site will not verify. Use verify_installation afterwards to confirm it is live.

NameTypeReqDescription
domainIdstring–Which domain’s tag to return, such as example.com. Omit it for the account’s default domain, the one the dashboard opens on.
NameTypeReqDescription
deferbooleanyesWhether the tag carries `defer`, which it does for a Shopify store.
domainIdstringyes–
isFromShopifybooleanyes–
nextStepstringyes–
placementstringyes–
scriptUrlstringyesThe banner script this domain’s tag loads.
snippetstringyesThe exact tag to paste, identical to the one the dashboard copies.
urlstringyes–

No examples provided.

get_scan_report ~114

Returns the latest cookie report for one of your CookiePal domains, with each cookie’s category, and says whether it came from a local scan. When a start_scan crawl is still running, reports that instead of an old report. The result reports what was found. It does not assess whether a site, page or banner complies with any law, so it is never a verdict of compliant or non-compliant.

NameTypeReqDescription
domainIdstring–Which domain to report on. Omit it for the account’s default domain.
NameTypeReqDescription
cookiesarrayyes–
domainIdstringyes–
localScanbooleanyes–
nextStepstringyes–
pagesScannednumberyes–
scannedAtstring|nullyes–
statusstringyes–
uniqueCookiesnumberyes–

No examples provided.

list_domains ~58

Lists the domains in the connected CookiePal account that this user can see, with each domain’s plan, this month’s page views, whether its page-view limit has been reached, and whether its banner has been found installed. Plans are per domain.

Input schema present but exposes no named parameters.

NameTypeReqDescription
domainsarrayyes–

No examples provided.

plan_check ~218

Starts a check of one web page for cookies set before consent. Returns a check ID and the plan the local check follows: the page is loaded in a browser on the user’s own computer, never by CookiePal, and the plan carries the banner matchers for pressing accept and reject there. Send the result to submit_check within 30 minutes. No account needed. The local run this needs is made only by the CookiePal plugin in a coding agent on the user’s own computer: Claude Code, Codex or Cursor. claude.ai, Claude Code on the web and other cloud agents run in the cloud, so they cannot make it, and a crawler or browser run anywhere else does not stand in for it.

NameTypeReqDescription
installIdstring–A random install ID, sent only when the user agreed to share it in the plugin. Omit it otherwise.
pluginVersionstring––
urlstringyesThe page to check, http or https, as origin and path only. CookiePal never requests it.
NameTypeReqDescription
captureobjectyes–
checkIdstringyes–
consentobjectyes–
expiresAtstringyesSubmit the result before this time.
limitsobjectyes–
loadobjectyes–
planVersionnumberyes–
ranFromobjectyes–
submitobjectyes–
targetobjectyes–

No examples provided.

regenerate_banner ~87

Queues a rebuild of the cookie banner script for one of your CookiePal domains, so it picks up the settings saved for it. It changes no setting and works on one domain only. If the domain has reached its page-view limit nothing is rebuilt, and the result says so.

NameTypeReqDescription
domainIdstring–Which domain to rebuild. Omit it for the account’s default domain.
NameTypeReqDescription
bannerEnabledbooleanyes–
domainIdstringyes–
messagestringyes–
rebuildstringyes–

No examples provided.

set_banner_mode ~115

Sets which privacy regulation one of your CookiePal domains’ banner follows: gdpr, ccpa or both, where both applies GDPR everywhere and CCPA to US visitors at the edge. It changes nothing else about the banner, and then queues a rebuild so the change goes live; if the domain has reached its page-view limit the rebuild is skipped, and the result says so.

NameTypeReqDescription
bannerModestringyes–
domainIdstring–Which domain to change. Omit it for the account’s default domain.
NameTypeReqDescription
bannerEnabledbooleanyes–
bannerModestringyes–
domainIdstringyes–
messagestringyes–
previousBannerModestringyes–
rebuildstringyes–

No examples provided.

start_scan ~205

Starts a crawl of one of your CookiePal domains on the user’s own computer, using the open-source crawl engine. CookiePal crawls nothing: run upload_scan_report with the result when the crawl finishes, and until then get_scan_report reports it as running. Needs the domain’s banner to be verified and active first, unless this is the very first scan of a domain just added with add_domain. The local run this needs is made only by the CookiePal plugin in a coding agent on the user’s own computer: Claude Code, Codex or Cursor. claude.ai, Claude Code on the web and other cloud agents run in the cloud, so they cannot make it, and a crawler or browser run anywhere else does not stand in for it.

NameTypeReqDescription
domainIdstring–Which domain to scan, such as example.com. Omit it for the account’s default domain.
maxPagesinteger–How many pages to crawl, up to 50.
NameTypeReqDescription
domainIdstringyes–
localScanbooleanyes–
maxPagesnumberyes–
nextStepstringyes–
pagesRemainingThisMonthnumberyes–
scanIdstringyes–
scanLimitnumberyes–
urlstringyes–

No examples provided.

submit_check ~353

Stores the result of a local check started with plan_check and returns it with a summary by category. Send each cookie with its category from @cookiepal-oss/cookie-db (necessary, functional, analytics, performance, advertisement or other) and its attributes, never its value. Include `consent` when the check pressed accept and reject, so the result says what survived an explicit reject. When no banner was found the result carries `noBannerSeenFrom`, the country the page was loaded from: a site that shows its banner only in other regions is indistinguishable from one with no banner, so that reading is inconclusive, not evidence that the site has no banner. Each check ID can be submitted once. The local run this needs is made only by the CookiePal plugin in a coding agent on the user’s own computer: Claude Code, Codex or Cursor. claude.ai, Claude Code on the web and other cloud agents run in the cloud, so they cannot make it, and a crawler or browser run anywhere else does not stand in for it. The result reports what was found. It does not assess whether a site, page or banner complies with any law, so it is never a verdict of compliant or non-compliant.

NameTypeReqDescription
checkIdstringyesThe check ID plan_check returned.
consentobject–What changed after accept and after reject. Omit it when the plugin did not run the consent action; the check is then an arrival-only reading.
cookiesarrayyes–
resultVersionnumberyes–
thirdPartyHostsarrayyes–
truncatedboolean–True when the skill dropped cookies or hosts to fit the limits.
NameTypeReqDescription
checkIdstringyes–
checkedAtstringyes–
consentobjectyes–
cookiesarrayyes–
countrystring|nullyes–
noBannerSeenFromstring|null––
pagestringyes–
resultVersionnumberyes–
summaryobjectyes–
thirdPartyHostsarrayyes–
truncatedbooleanyes–

No examples provided.

upload_scan_report ~235

Stores the result of a local crawl started with start_scan, as a report labelled a local scan. Send the cookies with their category from @cookiepal-oss/cookie-db. When robots.txt blocked the crawl, send blockedByRobots and no report is stored. Each scan ID can be uploaded once, by the user who started it. The local run this needs is made only by the CookiePal plugin in a coding agent on the user’s own computer: Claude Code, Codex or Cursor. claude.ai, Claude Code on the web and other cloud agents run in the cloud, so they cannot make it, and a crawler or browser run anywhere else does not stand in for it. The result reports what was found. It does not assess whether a site, page or banner complies with any law, so it is never a verdict of compliant or non-compliant.

NameTypeReqDescription
blockedByRobotsboolean––
cookiesarray––
pagesScannedinteger––
scanIdstringyes–
thirdPartyHostsarray––
truncatedboolean––
NameTypeReqDescription
byCategoryobjectyes–
cookiesStorednumberyes–
domainIdstringyes–
nextStepstringyes–
pagesScannednumberyes–
reportedAtstringyes–
scanSourcestringyes–

No examples provided.

verify_installation ~275

Records a check of one domain’s live page, loaded on the user’s own computer, and sets that domain’s banner verification status to verified or failed. Load the page locally first and send what it found: CookiePal never requests the page. The server compares the banner script the page loads with the one this domain’s tag must load, so a tag from another site, or a hand-built one, ends as failed with the reason. Nothing is crawled on CookiePal’s side. The local run this needs is made only by the CookiePal plugin in a coding agent on the user’s own computer: Claude Code, Codex or Cursor. claude.ai, Claude Code on the web and other cloud agents run in the cloud, so they cannot make it, and a crawler or browser run anywhere else does not stand in for it. The result reports what was found. It does not assess whether a site, page or banner complies with any law, so it is never a verdict of compliant or non-compliant.

NameTypeReqDescription
domainIdstring–Which domain was checked, such as example.com. Omit it for the account’s default domain.
evidenceobjectyesWhat the page load on the user’s computer found. Send it exactly as the local verify step returned it; never assemble or edit it.
NameTypeReqDescription
domainIdstringyes–
evidencestringyesThe reading was taken on the user’s computer, not by CookiePal. It is recorded as indicative.
expectedScriptUrlstringyesThe banner script this domain’s tag must load.
nextStepstringyes–
reasonstring|nullyesWhy the reading was not a verified install. Null when it was.
statusstringyesWhat the reading settled. `verified` and `failed` are the domain’s banner verification status, as this reading has just set it. `inconclusive` means the page could not be loaded, so nothing is known…
urlstringyesThe page that was read, as origin and path only: the query string and fragment are never stored or returned.
verifiedAtstringyes–

No examples provided.

whoami ~91

Reports the CookiePal account this client is signed in as: the user, the organisation, the domain tools act on by default, and each domain’s plan and whether its page-view limit has been reached. Use it to confirm a connection, or to find out which domain other tools will use when none is given.

NameTypeReqDescription
domainstring–The domain to report on. Defaults to the organisation’s current one.
NameTypeReqDescription
domainobjectyes–
domainPlansarrayyesEach domain this user can see, with its plan and whether this month’s page-view limit has been reached. Plans are per domain, not per account.
domainsarray––
emailstringyes–
organisationIdstringyes–
userIdstringyes–

No examples provided.

Install

How do I install the CookiePal MCP server?

CookiePal is a hosted endpoint at https://mcp.cookiepal.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · mcp.cookiepal.io

# add to Claude Code
claude mcp add --transport http io-cookiepal-cookiepal 'https://mcp.cookiepal.io/mcp'
Common questions

What is the CookiePal MCP server?

CookiePal is an MCP server listed in the public MCP registry as io.cookiepal/cookiepal. Manage your CookiePal cookie banner: domains, the banner tag and style, and cookie scan reports. This page covers its hosted endpoint (https://mcp.cookiepal.io/mcp).

Is the CookiePal MCP server safe to use?

CookiePal scores 70 out of 100 on VerifyMCP. 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 CookiePal MCP server expose?

CookiePal exposes 17 tools: plan_check, submit_check, forget_install, whoami, connect_account, and 12 more. Their descriptions and schemas cost roughly 2,929 tokens of context every time the server is loaded.

Does the CookiePal MCP server require authentication?

No. We connected to CookiePal without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the CookiePal MCP server still maintained?

CookiePal is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the CookiePal MCP server?

VerifyMCP ran 13 checks on CookiePal, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.