_ registry / mcp http-sse · checked 21m ago

kindnod

https://kindnod.com

Registry code: efe3df38ba0fa604

api record

GDPR cookie banner any coding agent can install with no account: provision, snippet, scan, verify.

from a public catalogue that lists it, not from the operator

endpoint
https://kindnod.com/api/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is kindnod live?
Yes — it answered the hub's last check (checked 21m ago). It answered 100% of checks over the last 30 days.
Is kindnod free to use?
Yes — the hub reached it with no key and no payment.
What tools does kindnod have?
5 tools: check_install, provision_site, scan_site, compare_cookiebot_cost, get_snippet.
Is kindnod safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
358ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 2 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 5 tools
1 open 4 never probed 1 of 5 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_snippet open 21m ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "via": {
          "type": "string"
        },
        "owner": {
          "type": "string",
          "description": "Site owner's email to put on the tag so they get the claim link"
        }
      },
      "additionalProperties": false
    }
    arguments 14 lines
  • check_install unknown 21m ago

    Fetches the live homepage and reports whether the Kindnod tag is present, whether a Cookiebot tag is still there, and whether the site is claimed.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "domain"
      ],
      "properties": {
        "domain": {
          "type": "string"
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • provision_site unknown never probed

    Creates (or finds) a free Kindnod 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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "domain"
      ],
      "properties": {
        "via": {
          "type": "string",
          "description": "Which tool is installing, e.g. claude-code, cursor, codex. Defaults to mcp"
        },
        "owner": {
          "type": "string",
          "description": "Site owner's email; Kindnod emails the claim link"
        },
        "domain": {
          "type": "string",
          "description": "Public hostname, e.g. example.com (no localhost)"
        }
      },
      "additionalProperties": false
    }
    arguments 22 lines
  • scan_site unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "url"
      ],
      "properties": {
        "url": {
          "type": "string",
          "description": "Site URL or domain"
        }
      },
      "additionalProperties": false
    }
    arguments 14 lines
  • compare_cookiebot_cost unknown never probed

    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 Kindnod's flat price. Sites with no consent tool get Cookiebot as the reference. The `incumbent.basis` field states the assumption behind the number.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "url"
      ],
      "properties": {
        "url": {
          "type": "string"
        },
        "domains": {
          "type": "integer",
          "maximum": 500,
          "minimum": 1,
          "description": "How many domains the account runs; agencies get a different Cookiebot tier"
        }
      },
      "additionalProperties": false
    }
    arguments 19 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id efe3df38ba0fa604.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/efe3df38ba0fa604/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/efe3df38ba0fa604/badge.svg)](https://brick.blue/agent/efe3df38ba0fa604?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
90%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.