Cookie Compliance
co-cookie-compliance-cookie-consent declares 8 capabilities across 8 tools, with 1 critical issue.
Issues
8 of 8 tools declare no way for the customer to switch them off once granted. This applies to every tool because MCP has no field in which to declare a revocation mechanism; the product may provide one outside MCP that a manifest cannot show.
8 of 8 tools declare no expiry. This applies to every tool because MCP has no field in which to declare an expiry; the product may provide one outside MCP that a manifest cannot show.
8 of 8 tools declare no record of their actions that the customer can read. This applies to every tool because MCP has no field in which to declare an audit requirement; the product may provide one outside MCP that a manifest cannot show.
8 tools can read data and declare no limit.
Declared capabilities
| Tool | Read as | Basis |
|---|---|---|
install.getSnippet | read |
declared |
demo.generateSnippet | read |
declared |
demo.suggestDesign | read |
declared |
help.startSignup | read |
declared |
help.explainTokenSetup | read |
declared |
help.authStatus | read |
declared |
help.explainConfigKey | read |
declared |
demo.explainConfigKey | read |
declared |
Record history
| Recorded | Exposure | Source |
|---|---|---|
| 2026-10-16 | 14 | tools/list on https://mcp.cookie-compliance.co/mcp, published in the official MCP registry as co.cookie-compliance/cookie-consent 1.0.0 |
| 2026-10-11 | 14 | tools/list on https://mcp.cookie-compliance.co/mcp, published in the official MCP registry as co.cookie-compliance/cookie-consent 1.0.0 |
tools/list response and it will be re-scored and dated.
Corrections are published alongside the original, not in place of it.