# CookiePal (remote · mcp.cookiepal.io)

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

- Trust score: 70/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `mcp.cookiepal.io`: 70/100 (this document), [markdown](https://verifymcp.io/servers/io-cookiepal-cookiepal/mcp.md), [page](https://verifymcp.io/servers/io-cookiepal-cookiepal/mcp)

## Channel facts

- Endpoint: `https://mcp.cookiepal.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (forget_install).
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 57/100
  - Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 91/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 70% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 17 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## 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.

### Claude

```bash
claude mcp add --transport http io-cookiepal-cookiepal 'https://mcp.cookiepal.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-cookiepal-cookiepal": {
      "url": "https://mcp.cookiepal.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-cookiepal-cookiepal": {
      "type": "http",
      "url": "https://mcp.cookiepal.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-cookiepal-cookiepal]
url = "https://mcp.cookiepal.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-cookiepal-cookiepal": {
      "type": "remote",
      "url": "https://mcp.cookiepal.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-cookiepal-cookiepal --url 'https://mcp.cookiepal.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-cookiepal-cookiepal:
    url: "https://mcp.cookiepal.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-cookiepal-cookiepal": {
      "Transport": "http",
      "Url": "https://mcp.cookiepal.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-cookiepal-cookiepal -t streamable-http -u 'https://mcp.cookiepal.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-cookiepal-cookiepal": {
      "type": "http",
      "url": "https://mcp.cookiepal.io/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-19 (score 70, +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.

### 2026-11-18 (score 69, 0)

- [security] Tool “customise_banner” rewrote its description, which is the text the model reads
- [cosmetic] “customise_banner” reworded the description of “logo”

### 2026-11-17 (score 69, +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.

### 2026-11-15 (score 68, +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.

### 2026-11-13 (score 67, +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.

### 2026-11-12 (score 66, 0)

- [security] 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
- [cosmetic] “plan_check” reworded the description of “url”

### 2026-11-11 (score 66, +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.

### 2026-11-09 (score 65, +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.

## MCP tools (17)

### `plan_check` (~218 tokens)

Plan a cookie check

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.

Input parameters:

- `installId` (string): A random install ID, sent only when the user agreed to share it in the plugin. Omit it otherwise.
- `pluginVersion` (string)
- `url` (string, required): The page to check, http or https, as origin and path only. CookiePal never requests it.

Output parameters:

- `capture` (object)
- `checkId` (string)
- `consent` (object)
- `expiresAt` (string): Submit the result before this time.
- `limits` (object)
- `load` (object)
- `planVersion` (number)
- `ranFrom` (object)
- `submit` (object)
- `target` (object)

### `submit_check` (~353 tokens)

Submit a cookie check

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.

Input parameters:

- `checkId` (string, required): The check ID plan_check returned.
- `consent` (object): 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.
- `cookies` (array, required)
- `resultVersion` (number, required)
- `thirdPartyHosts` (array, required)
- `truncated` (boolean): True when the skill dropped cookies or hosts to fit the limits.

Output parameters:

- `checkId` (string)
- `checkedAt` (string)
- `consent` (object)
- `cookies` (array)
- `country` (string|null)
- `noBannerSeenFrom` (string|null)
- `page` (string)
- `resultVersion` (number)
- `summary` (object)
- `thirdPartyHosts` (array)
- `truncated` (boolean)

### `forget_install` (~132 tokens)

Delete the checks stored under an install ID

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.

Input parameters:

- `installId` (string, required): The install ID to erase. Every check stored under it is deleted.

Output parameters:

- `deleted` (integer): How many stored checks were deleted. Zero is a normal answer.
- `remaining` (integer): Stored 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.
- `unlinked` (boolean): Whether the install ID was linked to a CookiePal account, and that link removed.

### `whoami` (~91 tokens)

Show the connected CookiePal account

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.

Input parameters:

- `domain` (string): The domain to report on. Defaults to the organisation’s current one.

Output parameters:

- `domain` (object)
- `domainPlans` (array): Each 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.
- `domains` (array)
- `email` (string)
- `organisationId` (string)
- `userId` (string)

### `connect_account` (~185 tokens)

Connect a CookiePal account

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.

Input parameters:

- `installId` (string): 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.
- `linkInstall` (boolean): 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.

Output parameters:

- `domain` (object)
- `email` (string)
- `installLinked` (boolean): Whether the install ID is linked to this account now, after this call.
- `installUnlinked` (boolean)
- `organisationId` (string)
- `organisationName` (string)
- `userId` (string)

### `list_domains` (~58 tokens)

List CookiePal domains

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.

Output parameters:

- `domains` (array)

### `add_domain` (~146 tokens)

Add a domain to CookiePal

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.

Input parameters:

- `domain` (string, required): The 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.

Output parameters:

- `addedToday` (number): Domains this organisation has added through the MCP server today, this one included.
- `bannerBuildQueued` (boolean)
- `dailyLimit` (number)
- `domainId` (string)
- `nextStep` (string)
- `plan` (string)
- `url` (string)

### `get_install_snippet` (~134 tokens)

Get the CookiePal banner install tag

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.

Input parameters:

- `domainId` (string): Which domain’s tag to return, such as example.com. Omit it for the account’s default domain, the one the dashboard opens on.

Output parameters:

- `defer` (boolean): Whether the tag carries `defer`, which it does for a Shopify store.
- `domainId` (string)
- `isFromShopify` (boolean)
- `nextStep` (string)
- `placement` (string)
- `scriptUrl` (string): The banner script this domain’s tag loads.
- `snippet` (string): The exact tag to paste, identical to the one the dashboard copies.
- `url` (string)

### `verify_installation` (~275 tokens)

Verify the CookiePal banner is installed

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.

Input parameters:

- `domainId` (string): Which domain was checked, such as example.com. Omit it for the account’s default domain.
- `evidence` (object, required): What the page load on the user’s computer found. Send it exactly as the local verify step returned it; never assemble or edit it.

Output parameters:

- `domainId` (string)
- `evidence` (string): The reading was taken on the user’s computer, not by CookiePal. It is recorded as indicative.
- `expectedScriptUrl` (string): The banner script this domain’s tag must load.
- `nextStep` (string)
- `reason` (string|null): Why the reading was not a verified install. Null when it was.
- `status` (string): What 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…
- `url` (string): The page that was read, as origin and path only: the query string and fragment are never stored or returned.
- `verifiedAt` (string)

### `start_scan` (~205 tokens)

Start a local cookie scan

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.

Input parameters:

- `domainId` (string): Which domain to scan, such as example.com. Omit it for the account’s default domain.
- `maxPages` (integer): How many pages to crawl, up to 50.

Output parameters:

- `domainId` (string)
- `localScan` (boolean)
- `maxPages` (number)
- `nextStep` (string)
- `pagesRemainingThisMonth` (number)
- `scanId` (string)
- `scanLimit` (number)
- `url` (string)

### `upload_scan_report` (~235 tokens)

Upload a local cookie scan

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.

Input parameters:

- `blockedByRobots` (boolean)
- `cookies` (array)
- `pagesScanned` (integer)
- `scanId` (string, required)
- `thirdPartyHosts` (array)
- `truncated` (boolean)

Output parameters:

- `byCategory` (object)
- `cookiesStored` (number)
- `domainId` (string)
- `nextStep` (string)
- `pagesScanned` (number)
- `reportedAt` (string)
- `scanSource` (string)

### `get_scan_report` (~114 tokens)

Get the latest cookie scan report

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.

Input parameters:

- `domainId` (string): Which domain to report on. Omit it for the account’s default domain.

Output parameters:

- `cookies` (array)
- `domainId` (string)
- `localScan` (boolean)
- `nextStep` (string)
- `pagesScanned` (number)
- `scannedAt` (string|null)
- `status` (string)
- `uniqueCookies` (number)

### `classify_cookies` (~89 tokens)

Classify cookies

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).

Input parameters:

- `cookies` (array, required)
- `domainId` (string): Which domain these cookies belong to. Omit it for the account’s default domain.

Output parameters:

- `domainId` (string)
- `results` (array)

### `check_gcm_status` (~245 tokens)

Check Google Consent Mode status

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.

Input parameters:

- `domainId` (string): Which domain was checked. Omit it for the account’s default domain.
- `reading` (object, required): Exactly what the gcm check command returned; never hand-built.
- `seenAt` (string, required): When the reading was taken, ISO 8601.
- `url` (string, required): The page that was read on the user’s computer.

Output parameters:

- `checkedAt` (string)
- `domainId` (string)
- `entriesMissingDefault` (array)
- `evidence` (string)
- `fix` (string)
- `nextStep` (string)
- `problem` (string)
- `status` (string)
- `title` (string)
- `url` (string)

### `set_banner_mode` (~115 tokens)

Set the banner mode

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.

Input parameters:

- `bannerMode` (string, required)
- `domainId` (string): Which domain to change. Omit it for the account’s default domain.

Output parameters:

- `bannerEnabled` (boolean)
- `bannerMode` (string)
- `domainId` (string)
- `message` (string)
- `previousBannerMode` (string)
- `rebuild` (string)

### `customise_banner` (~247 tokens)

Customise the banner

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.

Input parameters:

- `colors` (object): Only the colours you give change; the rest keep their saved value.
- `domainId` (string): Which domain to customise. Omit it for the account’s default domain.
- `logo` (object): 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.
- `positions` (object): Only the positions you give change; the rest keep their saved value.
- `texts` (array): Banner and preference-centre copy per language the banner already has, as plain text; paragraphs are separated by a blank line.

Output parameters:

- `bannerEnabled` (boolean)
- `domainId` (string)
- `message` (string)
- `rebuild` (string)
- `saved`
- `texts` (array)

### `regenerate_banner` (~87 tokens)

Rebuild the banner

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.

Input parameters:

- `domainId` (string): Which domain to rebuild. Omit it for the account’s default domain.

Output parameters:

- `bannerEnabled` (boolean)
- `domainId` (string)
- `message` (string)
- `rebuild` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-cookiepal-cookiepal/mcp#diagnostics

## Score history

- 2026-11-21: 70
- 2026-11-20: 70
- 2026-11-19: 70
- 2026-11-18: 69
- 2026-11-17: 69
- 2026-11-16: 68
- 2026-11-15: 68
- 2026-11-14: 67
- 2026-11-13: 67
- 2026-11-12: 66
- 2026-11-11: 66
- 2026-11-10: 65
- 2026-11-09: 65
- 2026-11-08: 64
- 2026-11-07: 64
- 2026-11-06: 63
- 2026-11-05: 63
- 2026-11-04: 63

## 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.

## Links

- Remote endpoint: https://mcp.cookiepal.io/mcp
- Website: https://cookiepal.io/ai
- Changelog RSS feed: https://verifymcp.io/servers/io-cookiepal-cookiepal/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-cookiepal-cookiepal/mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/io-cookiepal-cookiepal/mcp.json
- HTML version of this page: https://verifymcp.io/servers/io-cookiepal-cookiepal/mcp
