Remote MCP · Endpoint

Kindnod cookie consent MCP server

No. Kindnod cookie consent answered an MCP handshake 3 hours ago.

UpLast checked 3 hours ago

Server URL

https://kindnod.com/api/mcp

The last check completed an MCP handshake.

Registry name
com.kindnod/consent
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
203 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
GDPR cookie banner any coding agent can install with no account: provision, snippet, scan, verify.
Listing
From the official MCP registry (active).
Recent checks of Kindnod cookie consent
CheckedResultHandshake
3 hours agoHandshake completed203 ms
3 days agoHandshake completed233 ms
13 days agoHandshake completed157 ms
14 days agoHandshake completed220 ms
15 days agoHandshake completed160 ms
16 days agoHandshake completed210 ms
18 days agoHandshake completed158 ms
18 days agoHandshake completed237 ms
19 days agoHandshake completed171 ms
21 days agoHandshake completed288 ms
22 days agoHandshake completed277 ms
25 days agoHandshake completed200 ms
27 days agoHandshake completed976 ms

The last 13 checks. Full history is kept for 30 days; the all-time counter stands at 13 responding of 13.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with Kindnod cookie consent and makes no claim about it beyond what these checks measured.