render.com WebMCP audit

Rescan
audited Aug 28, 2026in 7s
63/ 100

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

WebMCP use71
Usefulness90
Human experience0
about:blank

No agent run recorded yet.

No steps recorded

Tools

/
render.docs.search: fail

render.docs.search

Search Render documentation by keyword.Answers a question. Declared read only.
pagehttps://render.com/
implementation
viaimperative
entry pointnavigator
registered after267ms
executepresent
api surface
queryrequired
annotations
read onlytrue
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: [/* ... */] });
warningNaming quality
1 / 2
Tool naming makes selection harder than it needs to be: names mix dot and other conventions; 5 names do not start with a verb (render.docs.search).
fix
{ name: "render.docs.search" /* short, unique, verb-based */ }
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.
render.docs.search, render.docs.get-markdown, render.llms.get-index, render.blog.get-index, render.articles.get-index
fix
<!-- Give the tool a visible counterpart: a declarative form is one the person can see and use too. -->
<form toolname="render.docs.search" tooldescription="...">
  <!-- the same action, as UI -->
</form>
tool json
{
  "name": "render.docs.search",
  "description": "Search Render documentation by keyword.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "query": {
        "type": "string",
        "description": "Keywords to search for in the Render docs."
      }
    },
    "required": [
      "query"
    ],
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  }
}
Showing render.docs.search

Findings

WebMCP use

71 / 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 267.09999990463257ms of navigation.
toolrender.docs.get-markdown
failCanonical entry point
0 / 4
Every tool registers through the deprecated navigator.modelContext alias; move them to document.modelContext before the alias is removed.
toolrender.docs.search
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.
passSchema quality
4 / 4
All 5 tool schemas describe their parameters and stay within Chrome's size guidance.
passStub detection
5 / 5
All 5 tools declare an execute handler.
passAnnotations present
4 / 4
All 5 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 (5 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.
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

90 / 100 · weight 30
warningNaming quality
1 / 2
Tool naming makes selection harder than it needs to be: names mix dot and other conventions; 5 names do not start with a verb (render.docs.search).
toolrender.docs.search
fix
{ name: "render.docs.search" /* 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.
passCoverage vs. site type
8 / 8
The tool set covers the whole core docs flow: search or browse the catalog, read a page or article, navigate the documentation tree.

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.
toolrender.docs.search
render.docs.search, render.docs.get-markdown, render.llms.get-index, render.blog.get-index, render.articles.get-index
fix
<!-- Give the tool a visible counterpart: a declarative form is one the person can see and use too. -->
<form toolname="render.docs.search" 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
7s
finished
Aug 28, 2026