Kindnod cookie consent
REMOTE · KINDNOD.COM
GDPR cookie banner any coding agent can install with no account: provision, snippet, scan, verify.
Available components
Last scanned (15 hours ago)
Scores higher than 74% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Security
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability70
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 443 tokens (~88/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage89
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 67% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
Checks we ran (12)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
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 →
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.
- 21 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 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 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 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 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 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 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Nov 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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://kindnod.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.kindnod.com | CN=YR1,O=Let's Encrypt,C=US | 22 Oct 2026 | 20 Jan 2027 | RSA 2048 | SHA256-RSA | 658f342f9ca3710370359923d0b0f3e8cbb |
| SANs: *.kindnod.com, kindnod.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of kindnod.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| kindnod.com. | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://kindnod.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://kindnod.com/api/mcp | HTTPS enforced | 308 | https://kindnod.com/api/mcp |
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 →
check_install Check whether Shortbread is live on a domain ~46
Fetches the live homepage and reports whether the Shortbread tag is present, whether a Cookiebot tag is still there, and whether the site is claimed.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | – |
No output schema declared.
No examples provided.
compare_cookiebot_cost Compare a site's consent tool price with Shortbread ~121
Scans the site, detects its consent tool (Cookiebot, iubenda, CookieYes, Termly, Cookie Script, Complianz, or others), maps the page count to that vendor's list tier, and returns the annual cost next to Shortbread's flat price. Sites with no consent tool get Cookiebot as the reference. The `incumbent.basis` field states the assumption behind the number.
| Name | Type | Req | Description |
|---|---|---|---|
| domains | integer | – | How many domains the account runs; agencies get a different Cookiebot tier |
| url | string | yes | – |
No output schema declared.
No examples provided.
get_snippet Get the Shortbread install snippet ~79
Returns the keyless install snippet (works for any public domain with no setup) and the npm usage for React/Next.js. Use provision_site instead when you want a site key and a claim link now.
| Name | Type | Req | Description |
|---|---|---|---|
| owner | string | – | Site owner's email to put on the tag so they get the claim link |
| via | string | – | – |
No output schema declared.
No examples provided.
provision_site Create a Shortbread site and get the install snippet ~134
Creates (or finds) a free Shortbread consent-banner site for a domain and returns the script tag to add before </head>, plus a claim URL the site owner uses to take over the dashboard. No account needed. Idempotent per domain. Pass the owner's email so the claim link is emailed to them.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Public hostname, e.g. example.com (no localhost) |
| owner | string | – | Site owner's email; Shortbread emails the claim link |
| via | string | – | Which tool is installing, e.g. claude-code, cursor, codex. Defaults to mcp |
No output schema declared.
No examples provided.
scan_site Scan a site for cookies and its current consent tool ~63
Fetches the homepage and a few internal pages, detects the platform, the current consent banner (Cookiebot, CookieYes, OneTrust…), tracking tools, and drafts a cookie declaration. Also counts pages from the sitemap.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Site URL or domain |
No output schema declared.
No examples provided.
How do I install the Kindnod cookie consent MCP server?
Kindnod cookie consent is a hosted endpoint at https://kindnod.com/api/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 · kindnod.com
claude mcp add --transport http com-kindnod-consent 'https://kindnod.com/api/mcp'
What is the Kindnod cookie consent MCP server?
Kindnod cookie consent is an MCP server listed in the public MCP registry as com.kindnod/consent. GDPR cookie banner any coding agent can install with no account: provision, snippet, scan, verify. This page covers its hosted endpoint (https://kindnod.com/api/mcp).
Is the Kindnod cookie consent MCP server safe to use?
Kindnod cookie consent scores 79 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 Kindnod cookie consent MCP server expose?
Kindnod cookie consent exposes 5 tools: provision_site, get_snippet, scan_site, compare_cookiebot_cost, check_install. Their descriptions and schemas cost roughly 443 tokens of context every time the server is loaded.
Does the Kindnod cookie consent MCP server require authentication?
No. We connected to Kindnod cookie consent without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Kindnod cookie consent MCP server still maintained?
Kindnod cookie consent 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 Kindnod cookie consent MCP server?
VerifyMCP ran 12 checks on Kindnod cookie consent, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Kindnod cookie consent: Authorization. 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.