pieverse.io WebMCP audit

Name: pieverse.io WebMCP audit
Creator: ora

Rescan

audited Aug 28, 2026in 5s

51/ 100

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

WebMCP use71

Usefulness50

Human experience0

about:blank

No agent run recorded yet.

No steps recorded

Tools

ask_pieverse_public_docs

Ask a read-only question about Pieverse public pricing, auth boundaries, sandbox, OpenAPI, or MCP resources.Answers a question. Declared read only.

pagehttps://www.pieverse.io/

implementation

viaimperative

entry pointdocument

registered after355ms

executepresent

api surface

queryrequired

annotations

read onlytrue

destructivefalse

idempotenttrue

open worldnot declared

untrusted contentfalse

titlenot declared

2 findings

warningSchema quality

0 / 4

2 of 2 tool schemas are harder for an agent to use than they need to be: ask_pieverse_public_docs 1 parameter has no description (query).

ask_pieverse_public_docs: 1 parameter has no description (query); batch_read_pieverse_public_resources: 1 parameter has no description (paths)

fix

{
  name: "ask_pieverse_public_docs",
  inputSchema: {
    type: "object",
    properties: {
      query: { type: "string", description: "What to search for" }
    },
    required: ["query"]
  }
}

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.

ask_pieverse_public_docs, batch_read_pieverse_public_resources

fix

<!-- Give the tool a visible counterpart: a declarative form is one the person can see and use too. -->
<form toolname="ask_pieverse_public_docs" tooldescription="...">
  <!-- the same action, as UI -->
</form>

tool json

{
  "name": "ask_pieverse_public_docs",
  "description": "Ask a read-only question about Pieverse public pricing, auth boundaries, sandbox, OpenAPI, or MCP resources.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "query": {
        "type": "string",
        "minLength": 1
      }
    },
    "required": [
      "query"
    ],
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true,
    "destructiveHint": false,
    "idempotentHint": true,
    "untrustedContentHint": false
  }
}

Findings

WebMCP use

71 / 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 355.2999999523163ms of navigation.

toolbatch_read_pieverse_public_resources

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.

warningSchema quality

0 / 4

2 of 2 tool schemas are harder for an agent to use than they need to be: ask_pieverse_public_docs 1 parameter has no description (query).

toolask_pieverse_public_docs

ask_pieverse_public_docs: 1 parameter has no description (query); batch_read_pieverse_public_resources: 1 parameter has no description (paths)

fix

{
  name: "ask_pieverse_public_docs",
  inputSchema: {
    type: "object",
    properties: {
      query: { type: "string", description: "What to search for" }
    },
    required: ["query"]
  }
}

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

50 / 100 · weight 30

warningNaming quality

1 / 2

Tool naming makes selection harder than it needs to be: 1 name is over Chrome's 30-character guidance; 2 names do not start with a verb (ask_pieverse_public_docs).

toolbatch_read_pieverse_public_resources

fix

{ name: "batch_read_pieverse_public_resources" /* 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

toolask_pieverse_public_docs

ask_pieverse_public_docs, batch_read_pieverse_public_resources

fix

<!-- Give the tool a visible counterpart: a declarative form is one the person can see and use too. -->
<form toolname="ask_pieverse_public_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