consentik.com WebMCP audit

Name: consentik.com WebMCP audit
Creator: ora

Rescan

audited Aug 28, 2026in 11s

57/ 100

3 tools registered. Strongest in usefulness, weakest in human experience.

WebMCP use55

Usefulness100

Human experience0

about:blank

No agent run recorded yet.

No steps recorded

Tools

check_cookie_compliance

Scan a website URL for GDPR cookie compliance, cookie categories, and consent banner detection using ConsentikTakes an action on the site.

pagehttps://consentik.com/

implementation

viaimperative

entry pointnavigator

registered after2015ms

executepresent

api surface

urlrequired

annotations

read onlynot declared

destructivenot declared

idempotentnot declared

open worldnot declared

untrusted contentnot declared

titlenot declared

3 findings

failCanonical entry point

0 / 4

Every tool registers through the deprecated navigator.modelContext alias; move them to document.modelContext before the alias is removed.

fix

// Use the canonical entry point - navigator.modelContext is deprecated.
document.modelContext.provideContext({ tools: [/* ... */] });

failAnnotations present

0 / 4

3 of 3 tools declare no readOnlyHint, so an agent cannot tell a read from a write without guessing from the name.

check_cookie_compliance, check_gcm_v2, get_consentik_pricing

fix

{
  name: "check_cookie_compliance",
  annotations: { readOnlyHint: true, destructiveHint: false, idempotentHint: true }
}

warningHuman parity

0 / 8

3 of 3 tools run through the JavaScript API with no visible counterpart, so the person co-browsing cannot see what the agent is offered. Declarative forms (or at least a title annotation) close the gap.

check_cookie_compliance, check_gcm_v2, get_consentik_pricing

fix

<!-- Give the tool a visible counterpart: a declarative form is one the person can see and use too. -->
<form toolname="check_cookie_compliance" tooldescription="...">
  <!-- the same action, as UI -->
</form>

tool json

{
  "name": "check_cookie_compliance",
  "description": "Scan a website URL for GDPR cookie compliance, cookie categories, and consent banner detection using Consentik",
  "inputSchema": {
    "type": "object",
    "properties": {
      "url": {
        "type": "string",
        "description": "The website URL to scan for cookie compliance"
      }
    },
    "required": [
      "url"
    ]
  },
  "annotations": {}
}

Findings

WebMCP use

55 / 100 · weight 50

passTools registered

4 / 4

3 tools registered across 1 page.

failReal-browser eligible

0 / 8

The page's code registers these tools, but a real visitor's browser does not get them yet: WebMCP needs a native modelContext or a current origin trial token, and this page has neither.

warningRegistration timing

2 / 4

The slowest tool took 2014.9000000953674ms to register, past the 1000ms an agent reading the registry at first paint would wait for.

toolcheck_gcm_v2

check_gcm_v2: registered at 2014.9000000953674ms

fix

// Register tools as soon as they're ready, not behind a deferred/async chunk.
document.modelContext.provideContext({ tools: [/* ... */] });

failCanonical entry point

0 / 4

Every tool registers through the deprecated navigator.modelContext alias; move them to document.modelContext before the alias is removed.

toolcheck_cookie_compliance

fix

// Use the canonical entry point - navigator.modelContext is deprecated.
document.modelContext.provideContext({ tools: [/* ... */] });

passSchema validity

5 / 5

All 3 tools declare a structurally valid object input schema.

passSchema quality

4 / 4

All 3 tool schemas describe their parameters and stay within Chrome's size guidance.

passStub detection

5 / 5

All 3 tools declare an execute handler.

failAnnotations present

0 / 4

3 of 3 tools declare no readOnlyHint, so an agent cannot tell a read from a write without guessing from the name.

toolcheck_cookie_compliance

check_cookie_compliance, check_gcm_v2, get_consentik_pricing

fix

{
  name: "check_cookie_compliance",
  annotations: { readOnlyHint: true, destructiveHint: false, idempotentHint: true }
}

not applicableAnnotation mismatch

0 / 3

No tool declares a readOnlyHint, so there is no safety claim to contradict.

not applicableUntrusted content hint

0 / 2

No tool's contract suggests it returns text written by somebody other than the site, so there is nothing to flag as untrusted.

passRegistration errors

2 / 2

No tool registration threw during the capture.

warningToolchange coherence

1 / 2

3 tools were registered but the page never dispatched a toolchange event, so an agent subscribed to registry updates never learns they exist.

fix

document.modelContext.dispatchEvent(new Event("toolchange"));

not applicableInjection surface

0 / 3

The injection-surface model hop returned no usable result, so tool contracts were not reviewed for injection surface.

Usefulness

100 / 100 · weight 30

passNaming quality

2 / 2

All 3 tool names are consistent, verb-led, and within Chrome's size guidance.

not applicableDescription quality

0 / 6

The description-quality model hop returned no usable result, so descriptions were not rated.

not applicableTool selection

0 / 14

The tool-selection model hop returned no usable result.

not applicableCoverage vs. site type

0 / 8

This tool set does not place the site in a category with a known expected tool shape, so there is no coverage baseline to score it against.

Human experience

0 / 100 · weight 20

warningHuman parity

0 / 8

toolcheck_cookie_compliance

check_cookie_compliance, check_gcm_v2, get_consentik_pricing

fix

<!-- Give the tool a visible counterpart: a declarative form is one the person can see and use too. -->
<form toolname="check_cookie_compliance" tooldescription="...">
  <!-- the same action, as UI -->
</form>

not applicablePage experience

0 / 12

The page-experience model hop returned no usable result, so the page was not graded.

Tool selection

The tool-selection model hop returned no usable result.

how this was captured

chrome: 148.0.7778.96
capture shim: v1
spec snapshot: 2026-08
mode: fast
pages: 1
tools: 3
run time: 11s
finished: Aug 28, 2026