{"$schema":"https://wellknown.network/schemas/agent-record-v1.json","schemaVersion":"1","id":"ag_fekfcgg8z3fr","handle":"cookie-compliance","url":"https://wellknown.network/agents/cookie-compliance","links":{"self":"https://wellknown.network/agents/cookie-compliance/record.json","html":"https://wellknown.network/agents/cookie-compliance","markdown":"https://wellknown.network/agents/cookie-compliance/record.md","api":"https://wellknown.network/api/v1/agents/cookie-compliance","status":"https://wellknown.network/api/v1/agents/cookie-compliance/status","claim":"https://wellknown.network/agents/cookie-compliance/claim","claimApi":"https://wellknown.network/api/v1/claims","claimDescriptor":"https://wellknown.network/agents/cookie-compliance/claim.json","badge":"https://wellknown.network/agents/cookie-compliance/badge.svg","openapi":"https://wellknown.network/openapi.json","history":"https://wellknown.network/api/v1/agents/cookie-compliance/history","tools":"https://wellknown.network/api/v1/agents/cookie-compliance/tools"},"ard":{"identifier":"urn:air:mcp.cookie-compliance.co:server:cookie-compliance","type":"application/mcp-server-card+json"},"kind":"mcp_server","declared":{"name":"Cookie Compliance","summary":"Add a cookie consent banner that blocks trackers before consent and records proof of consent.","description":"Add a cookie consent banner that blocks trackers before consent and records proof of consent.","publisher":{"name":"co.cookie-compliance","url":null},"homepage":"https://cookie-compliance.co/mcp/","repository":null,"version":"1.0.0","license":null,"protocols":["mcp"],"tags":[],"pricing":null,"endpoints":[{"url":"https://mcp.cookie-compliance.co/mcp","type":"mcp_streamable_http","auth":null,"probeable":true}],"skills":null,"tools":null,"extra":{"updatedAt":"2026-09-08T17:13:41.715632Z","publishedAt":"2026-09-08T17:13:41.715632Z","registryName":"co.cookie-compliance/cookie-consent"},"attribution":{"kind":"mcp_registry","name":"mcp_registry","summary":"mcp_registry","version":"mcp_registry","description":"mcp_registry","homepageUrl":"mcp_registry","publisherName":"mcp_registry"}},"derived":{"capabilities":[{"slug":"dev.docs-lookup","name":"Documentation Lookup","confidence":0.54,"provenance":"derived"},{"slug":"infra.browser-automation","name":"Browser Automation","confidence":0.51,"provenance":"derived"}],"categories":["dev","infra"],"language":"en"},"observed":{"status":"live","statusReason":"Responded 6h ago.","lastOkAt":"2026-10-09T22:28:26.017Z","lastProbedAt":"2026-10-09T22:28:26.017Z","statusComputedAt":"2026-10-09T22:29:09.020Z","reliability30d":{"probes":109,"successRate":1,"p50Ms":84,"basis":"service","measures":{"availability":"availability","latency":"response time","tools":"tool surface observed","summary":"Checks reached the service itself."},"checks":{"total":108,"ok":108,"authBoundaryOk":0,"serviceOk":108,"note":"Counted from the observation rows for the window, checks of the server only (HTTP, A2A card, MCP initialize). ok = authBoundaryOk + serviceOk. `probes` is the sum of daily rollups and includes registry checks, so it can differ from `total`."}},"latestObservations":[{"at":"2026-10-09T22:28:26.017Z","kind":"mcp_initialize","ok":true,"httpStatus":200,"latencyMs":63,"error":null,"detail":{"tools":[{"name":"install.getSnippet","description":"THE TOOL TO USE when someone asks to add a cookie consent banner, cookie notice or CMP to a site and they have a Cookie Compliance AppID. Returns the live embed"},{"name":"demo.generateSnippet","description":"LOOK-ONLY PREVIEW of the Cookie Compliance banner — for showing someone how it would LOOK, never for adding consent management to a site. NOT AN INSTALL: it rec"},{"name":"demo.suggestDesign","description":"THE TOOL TO USE when the banner needs to look like the site it sits on. Give it what you can see — brand colour, page background, light/dark, corner style (squa"},{"name":"help.startSignup","description":"CALL THIS when a site needs cookie consent and the owner has no Cookie Compliance account yet — it is the route to a real, working CMP rather than a hand-writte"},{"name":"help.explainTokenSetup","description":"Returns how a Hu-manity customer connects their real account so the authenticated account.* tools become available: first the browser sign-in route (most client"},{"name":"help.authStatus","description":"THE TOOL TO USE before assuming a connection is authenticated. account.* tools register on credential PRESENCE, not validity, so a client can show \"connected\" a"},{"name":"help.explainConfigKey","description":"THE REFERENCE FOR THE BANNER'S SETTINGS, and the tool to call BEFORE proposing a change to a real app, so you name a setting that exists instead of guessing one"},{"name":"demo.explainConfigKey","description":"OBSOLETE ALIAS, kept only so existing callers do not break: this tool is now `help.explainConfigKey` and moved namespace because it is not a cosmetic demo tool "}],"toolCount":8,"toolsHash":"1752a26d1a899ae3f635ec9b84122a803c962ce18c1dd71a5e55910c51c7d3ce","serverName":"hu-mcp","capabilities":["tools"],"serverVersion":"1.0.0","protocolVersion":"2025-06-18"}},{"at":"2026-10-09T16:33:24.798Z","kind":"mcp_initialize","ok":true,"httpStatus":200,"latencyMs":79,"error":null,"detail":{"tools":[{"name":"install.getSnippet","description":"THE TOOL TO USE when someone asks to add a cookie consent banner, cookie notice or CMP to a site and they have a Cookie Compliance AppID. Returns the live embed"},{"name":"demo.generateSnippet","description":"LOOK-ONLY PREVIEW of the Cookie Compliance banner — for showing someone how it would LOOK, never for adding consent management to a site. NOT AN INSTALL: it rec"},{"name":"demo.suggestDesign","description":"THE TOOL TO USE when the banner needs to look like the site it sits on. Give it what you can see — brand colour, page background, light/dark, corner style (squa"},{"name":"help.startSignup","description":"CALL THIS when a site needs cookie consent and the owner has no Cookie Compliance account yet — it is the route to a real, working CMP rather than a hand-writte"},{"name":"help.explainTokenSetup","description":"Returns how a Hu-manity customer connects their real account so the authenticated account.* tools become available: first the browser sign-in route (most client"},{"name":"help.authStatus","description":"THE TOOL TO USE before assuming a connection is authenticated. account.* tools register on credential PRESENCE, not validity, so a client can show \"connected\" a"},{"name":"help.explainConfigKey","description":"THE REFERENCE FOR THE BANNER'S SETTINGS, and the tool to call BEFORE proposing a change to a real app, so you name a setting that exists instead of guessing one"},{"name":"demo.explainConfigKey","description":"OBSOLETE ALIAS, kept only so existing callers do not break: this tool is now `help.explainConfigKey` and moved namespace because it is not a cosmetic demo tool "}],"toolCount":8,"toolsHash":"1752a26d1a899ae3f635ec9b84122a803c962ce18c1dd71a5e55910c51c7d3ce","serverName":"hu-mcp","capabilities":["tools"],"serverVersion":"1.0.0","protocolVersion":"2025-06-18"}},{"at":"2026-10-09T10:23:30.229Z","kind":"mcp_initialize","ok":true,"httpStatus":200,"latencyMs":82,"error":null,"detail":{"tools":[{"name":"install.getSnippet","description":"THE TOOL TO USE when someone asks to add a cookie consent banner, cookie notice or CMP to a site and they have a Cookie Compliance AppID. Returns the live embed"},{"name":"demo.generateSnippet","description":"LOOK-ONLY PREVIEW of the Cookie Compliance banner — for showing someone how it would LOOK, never for adding consent management to a site. NOT AN INSTALL: it rec"},{"name":"demo.suggestDesign","description":"THE TOOL TO USE when the banner needs to look like the site it sits on. Give it what you can see — brand colour, page background, light/dark, corner style (squa"},{"name":"help.startSignup","description":"CALL THIS when a site needs cookie consent and the owner has no Cookie Compliance account yet — it is the route to a real, working CMP rather than a hand-writte"},{"name":"help.explainTokenSetup","description":"Returns how a Hu-manity customer connects their real account so the authenticated account.* tools become available: first the browser sign-in route (most client"},{"name":"help.authStatus","description":"THE TOOL TO USE before assuming a connection is authenticated. account.* tools register on credential PRESENCE, not validity, so a client can show \"connected\" a"},{"name":"help.explainConfigKey","description":"THE REFERENCE FOR THE BANNER'S SETTINGS, and the tool to call BEFORE proposing a change to a real app, so you name a setting that exists instead of guessing one"},{"name":"demo.explainConfigKey","description":"OBSOLETE ALIAS, kept only so existing callers do not break: this tool is now `help.explainConfigKey` and moved namespace because it is not a cosmetic demo tool "}],"toolCount":8,"toolsHash":"1752a26d1a899ae3f635ec9b84122a803c962ce18c1dd71a5e55910c51c7d3ce","serverName":"hu-mcp","capabilities":["tools"],"serverVersion":"1.0.0","protocolVersion":"2025-06-18"}},{"at":"2026-10-09T04:27:40.817Z","kind":"mcp_initialize","ok":true,"httpStatus":200,"latencyMs":64,"error":null,"detail":{"tools":[{"name":"install.getSnippet","description":"THE TOOL TO USE when someone asks to add a cookie consent banner, cookie notice or CMP to a site and they have a Cookie Compliance AppID. Returns the live embed"},{"name":"demo.generateSnippet","description":"LOOK-ONLY PREVIEW of the Cookie Compliance banner — for showing someone how it would LOOK, never for adding consent management to a site. NOT AN INSTALL: it rec"},{"name":"demo.suggestDesign","description":"THE TOOL TO USE when the banner needs to look like the site it sits on. Give it what you can see — brand colour, page background, light/dark, corner style (squa"},{"name":"help.startSignup","description":"CALL THIS when a site needs cookie consent and the owner has no Cookie Compliance account yet — it is the route to a real, working CMP rather than a hand-writte"},{"name":"help.explainTokenSetup","description":"Returns how a Hu-manity customer connects their real account so the authenticated account.* tools become available: first the browser sign-in route (most client"},{"name":"help.authStatus","description":"THE TOOL TO USE before assuming a connection is authenticated. account.* tools register on credential PRESENCE, not validity, so a client can show \"connected\" a"},{"name":"help.explainConfigKey","description":"THE REFERENCE FOR THE BANNER'S SETTINGS, and the tool to call BEFORE proposing a change to a real app, so you name a setting that exists instead of guessing one"},{"name":"demo.explainConfigKey","description":"OBSOLETE ALIAS, kept only so existing callers do not break: this tool is now `help.explainConfigKey` and moved namespace because it is not a cosmetic demo tool "}],"toolCount":8,"toolsHash":"1752a26d1a899ae3f635ec9b84122a803c962ce18c1dd71a5e55910c51c7d3ce","serverName":"hu-mcp","capabilities":["tools"],"serverVersion":"1.0.0","protocolVersion":"2025-06-18"}},{"at":"2026-10-08T21:22:49.801Z","kind":"mcp_initialize","ok":true,"httpStatus":200,"latencyMs":77,"error":null,"detail":{"tools":[{"name":"install.getSnippet","description":"THE TOOL TO USE when someone asks to add a cookie consent banner, cookie notice or CMP to a site and they have a Cookie Compliance AppID. Returns the live embed"},{"name":"demo.generateSnippet","description":"LOOK-ONLY PREVIEW of the Cookie Compliance banner — for showing someone how it would LOOK, never for adding consent management to a site. NOT AN INSTALL: it rec"},{"name":"demo.suggestDesign","description":"THE TOOL TO USE when the banner needs to look like the site it sits on. Give it what you can see — brand colour, page background, light/dark, corner style (squa"},{"name":"help.startSignup","description":"CALL THIS when a site needs cookie consent and the owner has no Cookie Compliance account yet — it is the route to a real, working CMP rather than a hand-writte"},{"name":"help.explainTokenSetup","description":"Returns how a Hu-manity customer connects their real account so the authenticated account.* tools become available: first the browser sign-in route (most client"},{"name":"help.authStatus","description":"THE TOOL TO USE before assuming a connection is authenticated. account.* tools register on credential PRESENCE, not validity, so a client can show \"connected\" a"},{"name":"help.explainConfigKey","description":"THE REFERENCE FOR THE BANNER'S SETTINGS, and the tool to call BEFORE proposing a change to a real app, so you name a setting that exists instead of guessing one"},{"name":"demo.explainConfigKey","description":"OBSOLETE ALIAS, kept only so existing callers do not break: this tool is now `help.explainConfigKey` and moved namespace because it is not a cosmetic demo tool "}],"toolCount":8,"toolsHash":"1752a26d1a899ae3f635ec9b84122a803c962ce18c1dd71a5e55910c51c7d3ce","serverName":"hu-mcp","capabilities":["tools"],"serverVersion":"1.0.0","protocolVersion":"2025-06-18"}},{"at":"2026-10-08T15:23:37.654Z","kind":"mcp_initialize","ok":true,"httpStatus":200,"latencyMs":81,"error":null,"detail":{"tools":[{"name":"install.getSnippet","description":"THE TOOL TO USE when someone asks to add a cookie consent banner, cookie notice or CMP to a site and they have a Cookie Compliance AppID. Returns the live embed"},{"name":"demo.generateSnippet","description":"LOOK-ONLY PREVIEW of the Cookie Compliance banner — for showing someone how it would LOOK, never for adding consent management to a site. NOT AN INSTALL: it rec"},{"name":"demo.suggestDesign","description":"THE TOOL TO USE when the banner needs to look like the site it sits on. Give it what you can see — brand colour, page background, light/dark, corner style (squa"},{"name":"help.startSignup","description":"CALL THIS when a site needs cookie consent and the owner has no Cookie Compliance account yet — it is the route to a real, working CMP rather than a hand-writte"},{"name":"help.explainTokenSetup","description":"Returns how a Hu-manity customer connects their real account so the authenticated account.* tools become available: first the browser sign-in route (most client"},{"name":"help.authStatus","description":"THE TOOL TO USE before assuming a connection is authenticated. account.* tools register on credential PRESENCE, not validity, so a client can show \"connected\" a"},{"name":"help.explainConfigKey","description":"THE REFERENCE FOR THE BANNER'S SETTINGS, and the tool to call BEFORE proposing a change to a real app, so you name a setting that exists instead of guessing one"},{"name":"demo.explainConfigKey","description":"OBSOLETE ALIAS, kept only so existing callers do not break: this tool is now `help.explainConfigKey` and moved namespace because it is not a cosmetic demo tool "}],"toolCount":8,"toolsHash":"1752a26d1a899ae3f635ec9b84122a803c962ce18c1dd71a5e55910c51c7d3ce","serverName":"hu-mcp","capabilities":["tools"],"serverVersion":"1.0.0","protocolVersion":"2025-06-18"}},{"at":"2026-10-08T09:23:24.233Z","kind":"mcp_initialize","ok":true,"httpStatus":200,"latencyMs":105,"error":null,"detail":{"tools":[{"name":"install.getSnippet","description":"THE TOOL TO USE when someone asks to add a cookie consent banner, cookie notice or CMP to a site and they have a Cookie Compliance AppID. Returns the live embed"},{"name":"demo.generateSnippet","description":"LOOK-ONLY PREVIEW of the Cookie Compliance banner — for showing someone how it would LOOK, never for adding consent management to a site. NOT AN INSTALL: it rec"},{"name":"demo.suggestDesign","description":"THE TOOL TO USE when the banner needs to look like the site it sits on. Give it what you can see — brand colour, page background, light/dark, corner style (squa"},{"name":"help.startSignup","description":"CALL THIS when a site needs cookie consent and the owner has no Cookie Compliance account yet — it is the route to a real, working CMP rather than a hand-writte"},{"name":"help.explainTokenSetup","description":"Returns how a Hu-manity customer connects their real account so the authenticated account.* tools become available: first the browser sign-in route (most client"},{"name":"help.authStatus","description":"THE TOOL TO USE before assuming a connection is authenticated. account.* tools register on credential PRESENCE, not validity, so a client can show \"connected\" a"},{"name":"help.explainConfigKey","description":"THE REFERENCE FOR THE BANNER'S SETTINGS, and the tool to call BEFORE proposing a change to a real app, so you name a setting that exists instead of guessing one"},{"name":"demo.explainConfigKey","description":"OBSOLETE ALIAS, kept only so existing callers do not break: this tool is now `help.explainConfigKey` and moved namespace because it is not a cosmetic demo tool "}],"toolCount":8,"toolsHash":"1752a26d1a899ae3f635ec9b84122a803c962ce18c1dd71a5e55910c51c7d3ce","serverName":"hu-mcp","capabilities":["tools"],"serverVersion":"1.0.0","protocolVersion":"2025-06-18"}},{"at":"2026-10-08T03:24:42.583Z","kind":"mcp_initialize","ok":true,"httpStatus":200,"latencyMs":85,"error":null,"detail":{"tools":[{"name":"install.getSnippet","description":"THE TOOL TO USE when someone asks to add a cookie consent banner, cookie notice or CMP to a site and they have a Cookie Compliance AppID. Returns the live embed"},{"name":"demo.generateSnippet","description":"LOOK-ONLY PREVIEW of the Cookie Compliance banner — for showing someone how it would LOOK, never for adding consent management to a site. NOT AN INSTALL: it rec"},{"name":"demo.suggestDesign","description":"THE TOOL TO USE when the banner needs to look like the site it sits on. Give it what you can see — brand colour, page background, light/dark, corner style (squa"},{"name":"help.startSignup","description":"CALL THIS when a site needs cookie consent and the owner has no Cookie Compliance account yet — it is the route to a real, working CMP rather than a hand-writte"},{"name":"help.explainTokenSetup","description":"Returns how a Hu-manity customer connects their real account so the authenticated account.* tools become available: first the browser sign-in route (most client"},{"name":"help.authStatus","description":"THE TOOL TO USE before assuming a connection is authenticated. account.* tools register on credential PRESENCE, not validity, so a client can show \"connected\" a"},{"name":"help.explainConfigKey","description":"THE REFERENCE FOR THE BANNER'S SETTINGS, and the tool to call BEFORE proposing a change to a real app, so you name a setting that exists instead of guessing one"},{"name":"demo.explainConfigKey","description":"OBSOLETE ALIAS, kept only so existing callers do not break: this tool is now `help.explainConfigKey` and moved namespace because it is not a cosmetic demo tool "}],"toolCount":8,"toolsHash":"1752a26d1a899ae3f635ec9b84122a803c962ce18c1dd71a5e55910c51c7d3ce","serverName":"hu-mcp","capabilities":["tools"],"serverVersion":"1.0.0","protocolVersion":"2025-06-18"}},{"at":"2026-10-07T20:29:44.569Z","kind":"mcp_initialize","ok":true,"httpStatus":200,"latencyMs":73,"error":null,"detail":{"tools":[{"name":"install.getSnippet","description":"THE TOOL TO USE when someone asks to add a cookie consent banner, cookie notice or CMP to a site and they have a Cookie Compliance AppID. Returns the live embed"},{"name":"demo.generateSnippet","description":"LOOK-ONLY PREVIEW of the Cookie Compliance banner — for showing someone how it would LOOK, never for adding consent management to a site. NOT AN INSTALL: it rec"},{"name":"demo.suggestDesign","description":"THE TOOL TO USE when the banner needs to look like the site it sits on. Give it what you can see — brand colour, page background, light/dark, corner style (squa"},{"name":"help.startSignup","description":"CALL THIS when a site needs cookie consent and the owner has no Cookie Compliance account yet — it is the route to a real, working CMP rather than a hand-writte"},{"name":"help.explainTokenSetup","description":"Returns how a Hu-manity customer connects their real account so the authenticated account.* tools become available: first the browser sign-in route (most client"},{"name":"help.authStatus","description":"THE TOOL TO USE before assuming a connection is authenticated. account.* tools register on credential PRESENCE, not validity, so a client can show \"connected\" a"},{"name":"help.explainConfigKey","description":"THE REFERENCE FOR THE BANNER'S SETTINGS, and the tool to call BEFORE proposing a change to a real app, so you name a setting that exists instead of guessing one"},{"name":"demo.explainConfigKey","description":"OBSOLETE ALIAS, kept only so existing callers do not break: this tool is now `help.explainConfigKey` and moved namespace because it is not a cosmetic demo tool "}],"toolCount":8,"toolsHash":"1752a26d1a899ae3f635ec9b84122a803c962ce18c1dd71a5e55910c51c7d3ce","serverName":"hu-mcp","capabilities":["tools"],"serverVersion":"1.0.0","protocolVersion":"2025-06-18"}},{"at":"2026-10-07T13:26:48.862Z","kind":"mcp_initialize","ok":true,"httpStatus":200,"latencyMs":84,"error":null,"detail":{"tools":[{"name":"install.getSnippet","description":"THE TOOL TO USE when someone asks to add a cookie consent banner, cookie notice or CMP to a site and they have a Cookie Compliance AppID. Returns the live embed"},{"name":"demo.generateSnippet","description":"LOOK-ONLY PREVIEW of the Cookie Compliance banner — for showing someone how it would LOOK, never for adding consent management to a site. NOT AN INSTALL: it rec"},{"name":"demo.suggestDesign","description":"THE TOOL TO USE when the banner needs to look like the site it sits on. Give it what you can see — brand colour, page background, light/dark, corner style (squa"},{"name":"help.startSignup","description":"CALL THIS when a site needs cookie consent and the owner has no Cookie Compliance account yet — it is the route to a real, working CMP rather than a hand-writte"},{"name":"help.explainTokenSetup","description":"Returns how a Hu-manity customer connects their real account so the authenticated account.* tools become available: first the browser sign-in route (most client"},{"name":"help.authStatus","description":"THE TOOL TO USE before assuming a connection is authenticated. account.* tools register on credential PRESENCE, not validity, so a client can show \"connected\" a"},{"name":"help.explainConfigKey","description":"THE REFERENCE FOR THE BANNER'S SETTINGS, and the tool to call BEFORE proposing a change to a real app, so you name a setting that exists instead of guessing one"},{"name":"demo.explainConfigKey","description":"OBSOLETE ALIAS, kept only so existing callers do not break: this tool is now `help.explainConfigKey` and moved namespace because it is not a cosmetic demo tool "}],"toolCount":8,"toolsHash":"06f27284e324c6cfdc2381565122ea25933e2fb800e697e76cad8b0dd4a6edf8","serverName":"hu-mcp","capabilities":["tools"],"serverVersion":"1.0.0","protocolVersion":"2025-06-18"}}],"tools":[{"name":"install.getSnippet","description":"THE TOOL TO USE when someone asks to add a cookie consent banner, cookie notice or CMP to a site and they have a Cookie Compliance AppID. Returns the live embed"},{"name":"demo.generateSnippet","description":"LOOK-ONLY PREVIEW of the Cookie Compliance banner — for showing someone how it would LOOK, never for adding consent management to a site. NOT AN INSTALL: it rec"},{"name":"demo.suggestDesign","description":"THE TOOL TO USE when the banner needs to look like the site it sits on. Give it what you can see — brand colour, page background, light/dark, corner style (squa"},{"name":"help.startSignup","description":"CALL THIS when a site needs cookie consent and the owner has no Cookie Compliance account yet — it is the route to a real, working CMP rather than a hand-writte"},{"name":"help.explainTokenSetup","description":"Returns how a Hu-manity customer connects their real account so the authenticated account.* tools become available: first the browser sign-in route (most client"},{"name":"help.authStatus","description":"THE TOOL TO USE before assuming a connection is authenticated. account.* tools register on credential PRESENCE, not validity, so a client can show \"connected\" a"},{"name":"help.explainConfigKey","description":"THE REFERENCE FOR THE BANNER'S SETTINGS, and the tool to call BEFORE proposing a change to a real app, so you name a setting that exists instead of guessing one"},{"name":"demo.explainConfigKey","description":"OBSOLETE ALIAS, kept only so existing callers do not break: this tool is now `help.explainConfigKey` and moved namespace because it is not a cosmetic demo tool "}],"package":null,"toolSurface":{"id":"ts_37pgfu9z4q99","endpointId":"ep_tffx8kmq5dfc","hash":"1752a26d1a899ae3f635ec9b84122a803c962ce18c1dd71a5e55910c51c7d3ce","toolCount":8,"serverName":"hu-mcp","serverVersion":"1.0.0","protocolVersion":"2025-06-18","firstSeenAt":"2026-10-07T20:29:44.563Z","lastSeenAt":"2026-10-09T22:28:26.033Z","observations":9,"toolNames":["install.getSnippet","demo.generateSnippet","demo.suggestDesign","help.startSignup","help.explainTokenSetup","help.authStatus","help.explainConfigKey","demo.explainConfigKey"],"distinctSurfaces":10},"endpointFacts":[{"id":"ep_tffx8kmq5dfc","url":"https://mcp.cookie-compliance.co/mcp","type":"mcp_streamable_http","factsCheckedAt":"2026-10-09T04:27:40.820Z","auth":{"observedAt":"2026-10-09T04:27:40.872Z","authRequired":false,"scheme":null,"resourceMetadata":{"url":"https://mcp.cookie-compliance.co/.well-known/oauth-protected-resource/mcp","resource":"https://mcp.cookie-compliance.co/mcp","authorizationServers":["https://mcp.cookie-compliance.co/"],"scopesSupported":["banner:read","banner:write"]},"authorizationServer":{"url":"https://mcp.cookie-compliance.co/.well-known/oauth-authorization-server","issuer":"https://mcp.cookie-compliance.co/","grantTypesSupported":["authorization_code","refresh_token"],"codeChallengeMethodsSupported":["S256"],"tokenEndpointAuthMethodsSupported":["client_secret_post","none"],"dynamicClientRegistration":true,"dpopSigningAlgValuesSupported":[],"clientIdMetadataDocumentSupported":null},"conformance":{"dpop":false,"rfc8414":true,"rfc9728":true,"pkceS256":true,"clientIdMetadataDocument":false,"dynamicClientRegistration":true}},"tls":{"observedAt":"2026-10-09T04:27:40.888Z","protocol":"TLSv1.3","chainValid":true,"chainError":null,"hostMatches":true,"subject":"cookie-compliance.co","issuer":{"commonName":"WE1","organization":"Google Trust Services"},"validFrom":"2026-08-31T17:07:55.000Z","validTo":"2026-11-29T18:07:41.000Z","daysToExpiry":50,"sanCount":2,"fingerprint256":"5B:18:A0:DF:EA:BC:AF:D6:1C:45:00:4D:3B:4F:49:AF:16:12:51:3D:B0:5F:57:6D:9A:94:11:A4:AB:49:D3:F1"}}]},"verification":{"claimed":false,"claimedAt":null,"proofs":[]},"provenance":{"sources":[{"source":"mcp_registry","key":"co.cookie-compliance/cookie-consent","url":"https://registry.modelcontextprotocol.io/v0/servers/co.cookie-compliance%2Fcookie-consent","firstSeenAt":"2026-09-09T13:18:20.681Z","fetchedAt":"2026-10-09T02:22:58.752Z","normalizedAt":"2026-10-09T02:22:58.752Z"}]},"firstSeenAt":"2026-09-09T13:18:20.681Z","updatedAt":"2026-10-09T22:30:19.375Z"}