geosurge.ai WebMCP audit

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

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

WebMCP use60
Usefulness88
Human experience0
about:blank

No agent run recorded yet.

No steps recorded

Tools

/
search_geosurge: fail

search_geosurge

Search geoSurge's blog and content for a query. Returns matching articles as Markdown links with summaries.Takes an action on the site.
pagehttps://geosurge.ai/
implementation
viaimperative
entry pointnavigator
registered after832ms
executepresent
api surface
queryrequired
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
4 of 4 tools declare no readOnlyHint, so an agent cannot tell a read from a write without guessing from the name.
search_geosurge, list_articles, get_page_markdown, navigate
fix
{
  name: "search_geosurge",
  annotations: { readOnlyHint: true, destructiveHint: false, idempotentHint: true }
}
warningHuman parity
0 / 8
4 of 4 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.
search_geosurge, list_articles, get_page_markdown, navigate
fix
<!-- Give the tool a visible counterpart: a declarative form is one the person can see and use too. -->
<form toolname="search_geosurge" tooldescription="...">
  <!-- the same action, as UI -->
</form>
tool json
{
  "name": "search_geosurge",
  "description": "Search geoSurge's blog and content for a query. Returns matching articles as Markdown links with summaries.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "query": {
        "type": "string",
        "description": "Search terms"
      }
    },
    "required": [
      "query"
    ]
  },
  "annotations": {}
}
Showing search_geosurge

Findings

WebMCP use

60 / 100 · weight 50
passTools registered
4 / 4
4 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 832.6000001430511ms of navigation.
toollist_articles
failCanonical entry point
0 / 4
Every tool registers through the deprecated navigator.modelContext alias; move them to document.modelContext before the alias is removed.
toolsearch_geosurge
fix
// Use the canonical entry point - navigator.modelContext is deprecated.
document.modelContext.provideContext({ tools: [/* ... */] });
passSchema validity
5 / 5
All 4 tools declare a structurally valid object input schema.
passSchema quality
4 / 4
All 4 tool schemas describe their parameters and stay within Chrome's size guidance.
passStub detection
5 / 5
All 4 tools declare an execute handler.
failAnnotations present
0 / 4
4 of 4 tools declare no readOnlyHint, so an agent cannot tell a read from a write without guessing from the name.
toolsearch_geosurge
search_geosurge, list_articles, get_page_markdown, navigate
fix
{
  name: "search_geosurge",
  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
4 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

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