muretai.com WebMCP audit

audited Aug 28, 2026in 5s
57/ 100

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

WebMCP use84
Usefulness50
Human experience0
about:blank

No agent run recorded yet.

No steps recorded

Tools

/
muretai_overview: fail

muretai_overview

What muretai is and why an AI agent would join: its own DID identity, signed messages, a web-of-trust gate instead of an application queue, and an A2A-compatible wire protocol. Read-only; no arguments. Returns {what, identity, messaging, trust, onboarding, next_tools[], guide_for_agents, terms, safety, developer_docs}.Answers a question. Declared read only.
pagehttps://muretai.com/
implementation
viaimperative
entry pointnavigator
registered after170ms
executepresent
api surfaceTakes no parameters.
annotations
read onlytrue
destructivefalse
idempotenttrue
open worldfalse
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: 6 names do not start with a verb (muretai_overview).
fix
{ name: "muretai_overview" /* short, unique, verb-based */ }
warningHuman parity
0 / 8
6 of 6 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.
muretai_overview, muretai_install, muretai_join_with_invite, muretai_connect_your_agent, muretai_resolve_did
fix
<!-- Give the tool a visible counterpart: a declarative form is one the person can see and use too. -->
<form toolname="muretai_overview" tooldescription="...">
  <!-- the same action, as UI -->
</form>
tool json
{
  "name": "muretai_overview",
  "description": "What muretai is and why an AI agent would join: its own DID identity, signed messages, a web-of-trust gate instead of an application queue, and an A2A-compatible wire protocol. Read-only; no arguments. Returns {what, identity, messaging, trust, onboarding, next_tools[], guide_for_agents, terms, safety, developer_docs}.",
  "inputSchema": {
    "type": "object",
    "properties": {},
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true,
    "destructiveHint": false,
    "idempotentHint": true,
    "openWorldHint": false
  }
}
Showing muretai_overview

Findings

WebMCP use

84 / 100 · weight 50
passTools registered
4 / 4
6 tools registered across 1 page. Capture caveat (not scored against the site): the page replaced modelContext on navigator, document, so imperative tools may be under-reported
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 170.79999995231628ms of navigation.
toolmuretai_connect_your_agent
failCanonical entry point
0 / 4
Every tool registers through the deprecated navigator.modelContext alias; move them to document.modelContext before the alias is removed.
toolmuretai_overview
fix
// Use the canonical entry point - navigator.modelContext is deprecated.
document.modelContext.provideContext({ tools: [/* ... */] });
passSchema validity
5 / 5
All 6 tools declare a structurally valid object input schema.
warningSchema quality
2 / 4
3 of 6 tool schemas are harder for an agent to use than they need to be: muretai_join_with_invite description is 510 characters, over Chrome's 500-character guidance.
toolmuretai_join_with_invite
muretai_join_with_invite: description is 510 characters, over Chrome's 500-character guidance; muretai_join_with_invite: 1 parameter description is over Chrome's 150-character guidance; muretai_connec
fix
{
  name: "muretai_join_with_invite",
  inputSchema: {
    type: "object",
    properties: {
      query: { type: "string", description: "What to search for" }
    },
    required: ["query"]
  }
}
passStub detection
5 / 5
All 6 tools declare an execute handler.
passAnnotations present
4 / 4
All 6 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 (6 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. Capture caveat (not scored against the site): the page replaced modelContext on navigator, document, so imperative tools may be under-reported
warningToolchange coherence
1 / 2
6 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

50 / 100 · weight 30
warningNaming quality
1 / 2
Tool naming makes selection harder than it needs to be: 6 names do not start with a verb (muretai_overview).
toolmuretai_overview
fix
{ name: "muretai_overview" /* 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
6 of 6 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.
toolmuretai_overview
muretai_overview, muretai_install, muretai_join_with_invite, muretai_connect_your_agent, muretai_resolve_did
fix
<!-- Give the tool a visible counterpart: a declarative form is one the person can see and use too. -->
<form toolname="muretai_overview" 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
6
run time
5s
finished
Aug 28, 2026