audit.wordlift.io WebMCP audit

Rescan
audited Aug 28, 2026in 6s
42/ 100

One tool registered. Strongest in WebMCP use, weakest in human experience.

WebMCP use55
Usefulness50
Human experience0
about:blank

No agent run recorded yet.

No steps recorded

Tools

/
run-audit: fail

run-audit

Run a full AI readiness audit on a given URL. Returns a structured report with an overall score (0–100) plus detailed findings for site files, SEO fundamentals, structured data, content structure, image accessibility, automation readiness, and JavaScript rendering.Takes an action on the site.
pagehttps://audit.wordlift.io/
implementation
viaimperative
entry pointnavigator
registered after1574ms
executepresent
api surface
urlrequired
annotations
read onlynot declared
destructivenot declared
idempotentnot declared
open worldnot declared
untrusted contentnot declared
titlenot declared
5 findings
warningRegistration timing
2 / 4
The slowest tool took 1573.7000000476837ms to register, past the 1000ms an agent reading the registry at first paint would wait for.
run-audit: registered at 1573.7000000476837ms
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.
fix
// Use the canonical entry point - navigator.modelContext is deprecated.
document.modelContext.provideContext({ tools: [/* ... */] });
warningNaming quality
1 / 2
Tool naming makes selection harder than it needs to be: 1 name does not start with a verb (run-audit).
fix
{ name: "run-audit" /* short, unique, verb-based */ }
failAnnotations present
0 / 4
1 of 1 tools declare no readOnlyHint, so an agent cannot tell a read from a write without guessing from the name.
run-audit
fix
{
  name: "run-audit",
  annotations: { readOnlyHint: true, destructiveHint: false, idempotentHint: true }
}
warningHuman parity
0 / 8
1 of 1 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.
run-audit
fix
<!-- Give the tool a visible counterpart: a declarative form is one the person can see and use too. -->
<form toolname="run-audit" tooldescription="...">
  <!-- the same action, as UI -->
</form>
tool json
{
  "name": "run-audit",
  "description": "Run a full AI readiness audit on a given URL. Returns a structured report with an overall score (0–100) plus detailed findings for site files, SEO fundamentals, structured data, content structure, image accessibility, automation readiness, and JavaScript rendering.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "url": {
        "type": "string",
        "description": "The fully-qualified URL to audit (e.g. https://example.com). Must be a public, accessible page."
      }
    },
    "required": [
      "url"
    ]
  },
  "annotations": {}
}
Showing run-audit

Findings

WebMCP use

55 / 100 · weight 50
passTools registered
4 / 4
1 tool 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 1573.7000000476837ms to register, past the 1000ms an agent reading the registry at first paint would wait for.
toolrun-audit
run-audit: registered at 1573.7000000476837ms
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.
toolrun-audit
fix
// Use the canonical entry point - navigator.modelContext is deprecated.
document.modelContext.provideContext({ tools: [/* ... */] });
passSchema validity
5 / 5
All 1 tool declare a structurally valid object input schema.
passSchema quality
4 / 4
All 1 tool schema describe their parameters and stay within Chrome's size guidance.
passStub detection
5 / 5
The one registered tool declares an execute handler.
failAnnotations present
0 / 4
1 of 1 tools declare no readOnlyHint, so an agent cannot tell a read from a write without guessing from the name.
toolrun-audit
run-audit
fix
{
  name: "run-audit",
  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
1 tool was 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

50 / 100 · weight 30
warningNaming quality
1 / 2
Tool naming makes selection harder than it needs to be: 1 name does not start with a verb (run-audit).
toolrun-audit
fix
{ name: "run-audit" /* short, unique, verb-based */ }
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
1 of 1 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.
toolrun-audit
run-audit
fix
<!-- Give the tool a visible counterpart: a declarative form is one the person can see and use too. -->
<form toolname="run-audit" 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
1
run time
6s
finished
Aug 28, 2026