docs.dify.ai WebMCP audit

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

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

WebMCP use80
Usefulness68
Human experience0
about:blank

No agent run recorded yet.

No steps recorded

Tools

/en/home
search_docs: warning

search_docs

Search the documentation for relevant pages and content.Answers a question. Declared read only.
pagehttps://docs.dify.ai/en/home
implementation
viaimperative
entry pointdocument
registered after823ms
executepresent
api surface
queryrequired
annotations
read onlytrue
destructivenot declared
idempotentnot declared
open worldnot declared
untrusted contenttrue
titlenot declared
1 finding
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.
search_docs, open_skill
fix
<!-- Give the tool a visible counterpart: a declarative form is one the person can see and use too. -->
<form toolname="search_docs" tooldescription="...">
  <!-- the same action, as UI -->
</form>
tool json
{
  "name": "search_docs",
  "description": "Search the documentation for relevant pages and content.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "query": {
        "type": "string",
        "description": "Search query"
      }
    },
    "required": [
      "query"
    ],
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true,
    "untrustedContentHint": true
  }
}
Showing search_docs

Findings

WebMCP use

80 / 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 822.8999998569489ms of navigation.
toolopen_skill
passCanonical entry point
4 / 4
All 2 tools register on the canonical document.modelContext entry point.
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.
passRegistration errors
2 / 2
No tool registration threw during the capture.
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

68 / 100 · weight 30
warningNaming quality
1.5 / 2
Tool naming makes selection harder than it needs to be: 1 name does not start with a verb (open_skill).
toolopen_skill
fix
{ name: "open_skill" /* 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.
warningCoverage vs. site type
5.3 / 8
The tool set covers 2 of the 3 things an agent needs on a docs site; it cannot navigate the documentation tree.

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.
toolsearch_docs
search_docs, open_skill
fix
<!-- Give the tool a visible counterpart: a declarative form is one the person can see and use too. -->
<form toolname="search_docs" 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
5s
finished
Aug 28, 2026