node8.ai WebMCP audit

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

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

WebMCP use87
Usefulness38
Human experience0
about:blank

No agent run recorded yet.

No steps recorded

Tools

/
get_company_info: warning

get_company_info

Returns structured information about Node8 — what the company does, its three-step service model, ideal customer profile, and technology partners. Use this first to understand if Node8 is a fit.Answers a question. Declared read only.
pagehttps://node8.ai/
implementation
viaimperative
entry pointdocument
registered after376ms
executepresent
api surfaceTakes no parameters.
annotations
read onlytrue
destructivenot declared
idempotentnot declared
open worldnot declared
untrusted contentnot declared
titlenot declared
2 findings
warningUntrusted content hint
0 / 2
1 of 1 tools look like they return text written by other people but declare no untrustedContentHint, so an agent will treat the response as the site speaking.
get_company_info: profile, customer
fix
{ name: "get_company_info", annotations: { untrustedContentHint: 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.
get_company_info, navigate_to_solution, book_discovery_call, submit_inquiry
fix
<!-- Give the tool a visible counterpart: a declarative form is one the person can see and use too. -->
<form toolname="get_company_info" tooldescription="...">
  <!-- the same action, as UI -->
</form>
tool json
{
  "name": "get_company_info",
  "description": "Returns structured information about Node8 — what the company does, its three-step service model, ideal customer profile, and technology partners. Use this first to understand if Node8 is a fit.",
  "inputSchema": {
    "type": "object",
    "properties": {}
  },
  "annotations": {
    "readOnlyHint": true
  }
}
Showing get_company_info

Findings

WebMCP use

87 / 100 · weight 50
passTools registered
4 / 4
4 tools registered across 1 page.
passReal-browser eligible
8 / 8
A real browser exposes modelContext natively on this page, so the tools registered here are visible to an agent today.
passRegistration timing
4 / 4
Every measured tool registered within 376.59999990463257ms of navigation.
toolsubmit_inquiry
passCanonical entry point
4 / 4
All 4 tools register on the canonical document.modelContext entry point.
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.
warningAnnotations present
1 / 4
3 of 4 tools declare no readOnlyHint, so an agent cannot tell a read from a write without guessing from the name.
toolnavigate_to_solution
navigate_to_solution, book_discovery_call, submit_inquiry
fix
{
  name: "navigate_to_solution",
  annotations: { readOnlyHint: true, destructiveHint: false, idempotentHint: true }
}
passAnnotation mismatch
3 / 3
No tool claims to be read-only while its name says it writes (1 declared hint checked).
warningUntrusted content hint
0 / 2
1 of 1 tools look like they return text written by other people but declare no untrustedContentHint, so an agent will treat the response as the site speaking.
toolget_company_info
get_company_info: profile, customer
fix
{ name: "get_company_info", annotations: { untrustedContentHint: true } }
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

38 / 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_to_solution).
toolnavigate_to_solution
fix
{ name: "navigate_to_solution" /* 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.
failCoverage vs. site type
2 / 8
The tool set covers 1 of the 4 things an agent needs on a saas site; it cannot search or browse the catalog or create a record or start a job or update or move an existing record.

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.
toolget_company_info
get_company_info, navigate_to_solution, book_discovery_call, submit_inquiry
fix
<!-- Give the tool a visible counterpart: a declarative form is one the person can see and use too. -->
<form toolname="get_company_info" 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
6s
finished
Aug 28, 2026