reflex.dev WebMCP audit

audited Aug 28, 2026in 6s
52/ 100

2 tools registered. Strongest in WebMCP use, weakest in human experience.

WebMCP use73
Usefulness50
Human experience0
about:blank

No agent run recorded yet.

No steps recorded

Tools

/
navigate_reflex: warning

navigate_reflex

Navigate to a path on reflex.dev (e.g. "/docs/getting-started/introduction", "/pricing", "/blog").Takes an action on the site.
pagehttps://reflex.dev/
implementation
viaimperative
entry pointnavigator
registered after302ms
executepresent
api surface
pathrequired
annotations
read onlyfalse
destructivenot declared
idempotentnot declared
open worldnot declared
untrusted contentfalse
titlenot declared
4 findings
passRegistration timing
4 / 4
Every measured tool registered within 302ms of navigation.
warningCanonical entry point
2 / 4
1 of 2 tools still register through the deprecated navigator.modelContext alias.
navigate_reflex
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: 2 names do not start with a verb (navigate_reflex).
fix
{ name: "navigate_reflex" /* short, unique, verb-based */ }
warningHuman parity
0 / 8
2 of 2 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.
navigate_reflex, navigate_reflex
fix
<!-- Give the tool a visible counterpart: a declarative form is one the person can see and use too. -->
<form toolname="navigate_reflex" tooldescription="...">
  <!-- the same action, as UI -->
</form>
tool json
{
  "name": "navigate_reflex",
  "description": "Navigate to a path on reflex.dev (e.g. \"/docs/getting-started/introduction\", \"/pricing\", \"/blog\").",
  "inputSchema": {
    "type": "object",
    "properties": {
      "path": {
        "type": "string",
        "description": "Path on reflex.dev, starting with \"/\"."
      }
    },
    "required": [
      "path"
    ]
  },
  "annotations": {
    "readOnlyHint": false,
    "untrustedContentHint": false
  }
}
Showing navigate_reflex

Findings

WebMCP use

73 / 100 · weight 50
passTools registered
4 / 4
2 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.
passRegistration timing
4 / 4
Every measured tool registered within 302ms of navigation.
toolnavigate_reflex
warningCanonical entry point
2 / 4
1 of 2 tools still register through the deprecated navigator.modelContext alias.
toolnavigate_reflex
navigate_reflex
fix
// Use the canonical entry point - navigator.modelContext is deprecated.
document.modelContext.provideContext({ tools: [/* ... */] });
passSchema validity
5 / 5
All 2 tools declare a structurally valid object input schema.
passSchema quality
4 / 4
All 2 tool schemas describe their parameters and stay within Chrome's size guidance.
passStub detection
5 / 5
All 2 tools declare an execute handler.
passAnnotations present
4 / 4
All 2 tools declare a readOnlyHint, so an agent knows which calls change state.
passAnnotation mismatch
3 / 3
No tool claims to be read-only while its name says it writes (2 declared hints checked).
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.
warningRegistration errors
1 / 2
1 tool registration threw during the capture, so the registry an agent reads is incomplete.
duplicate tool name registered: navigate_reflex
fix
try {
  document.modelContext.provideContext({ tools: [/* ... */] });
} catch (err) {
  console.error("WebMCP registration failed", err);
}
warningToolchange coherence
1 / 2
2 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

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