openfort.io WebMCP audit

Rescan
audited Aug 28, 2026in 5s
53/ 100

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

WebMCP use58
Usefulness80
Human experience0
about:blank

No agent run recorded yet.

No steps recorded

Tools

/
navigate_to_page: fail

navigate_to_page

Navigate the browser to a page on openfort.io. Use this to move the user to a relevant section of the site.Takes an action on the site.
pagehttps://www.openfort.io/
implementation
viaimperative
entry pointnavigator
registered after633ms
executepresent
api surface
pagerequired
annotations
read onlynot declared
destructivenot declared
idempotentnot declared
open worldnot declared
untrusted contentnot declared
titlenot declared
4 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: [/* ... */] });
warningNaming quality
1.6 / 2
Tool naming makes selection harder than it needs to be: 2 names do not start with a verb (navigate_to_page).
fix
{ name: "navigate_to_page" /* short, unique, verb-based */ }
failAnnotations present
0 / 4
5 of 5 tools declare no readOnlyHint, so an agent cannot tell a read from a write without guessing from the name.
navigate_to_page, search_docs, list_sdks, contact_sales, get_api_references
fix
{
  name: "navigate_to_page",
  annotations: { readOnlyHint: true, destructiveHint: false, idempotentHint: true }
}
warningHuman parity
0 / 8
5 of 5 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_to_page, search_docs, list_sdks, contact_sales, get_api_references
fix
<!-- Give the tool a visible counterpart: a declarative form is one the person can see and use too. -->
<form toolname="navigate_to_page" tooldescription="...">
  <!-- the same action, as UI -->
</form>
tool json
{
  "name": "navigate_to_page",
  "description": "Navigate the browser to a page on openfort.io. Use this to move the user to a relevant section of the site.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "page": {
        "type": "string",
        "enum": [
          "home",
          "pricing",
          "embedded-wallet",
          "wallet-as-a-service",
          "account-abstraction",
          "authentication",
          "wallet-automations",
          "security",
          "customers",
          "blog",
          "changelog",
          "benchmarks",
          "compare",
          "docs"
        ],
        "description": "Short key for a known page."
      }
    },
    "required": [
      "page"
    ]
  },
  "annotations": {}
}
Showing navigate_to_page

Findings

WebMCP use

58 / 100 · weight 50
passTools registered
4 / 4
5 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 634.2000000476837ms of navigation.
toolget_api_references
failCanonical entry point
0 / 4
Every tool registers through the deprecated navigator.modelContext alias; move them to document.modelContext before the alias is removed.
toolnavigate_to_page
fix
// Use the canonical entry point - navigator.modelContext is deprecated.
document.modelContext.provideContext({ tools: [/* ... */] });
passSchema validity
5 / 5
All 5 tools declare a structurally valid object input schema.
warningSchema quality
3.2 / 4
1 of 5 tool schemas are harder for an agent to use than they need to be: search_docs declares no required list, so an agent cannot tell which parameters are mandatory.
toolsearch_docs
search_docs: declares no required list, so an agent cannot tell which parameters are mandatory
fix
{
  name: "search_docs",
  inputSchema: {
    type: "object",
    properties: {
      query: { type: "string", description: "What to search for" }
    },
    required: ["query"]
  }
}
passStub detection
5 / 5
All 5 tools declare an execute handler.
failAnnotations present
0 / 4
5 of 5 tools declare no readOnlyHint, so an agent cannot tell a read from a write without guessing from the name.
toolnavigate_to_page
navigate_to_page, search_docs, list_sdks, contact_sales, get_api_references
fix
{
  name: "navigate_to_page",
  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
5 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

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