sentry.io WebMCP audit

Name: sentry.io WebMCP audit
Creator: ora

Rescan

audited Sep 1, 2026in 14s

65/ 100100% of the applicable check weight evaluated

6 tools registered. Strongest in shared experience, weakest in trust.

Shared experience100

Task completion47

Tool quality92

Trust0

https://sentry.io

Tools

0 read, 0 write, 6 undeclared

Loading map

start_signup

Open Sentry's free sign-up flow in a new tab so a user can create an account.No behaviour hints declared. Agents should treat it as possibly state-changing.

pagehttps://sentry.io/welcome/

implementation

viaimperative

entry pointprovideContext

registered after905ms

executepresent

api surface

sourceoptional

annotations

read onlynot declared

untrusted contentnot declared

titlenot declared

1 finding

warningSchema quality

weight 4

2 of 6 tool schemas are harder for an agent to use than they need to be: start_signup declares no required list, so an agent cannot tell which parameters are mandatory.

start_signup: declares no required list, so an agent cannot tell which parameters are mandatory; open_product_page: 1 parameter has no description (product)

fix

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

tool json

{
  "name": "start_signup",
  "description": "Open Sentry's free sign-up flow in a new tab so a user can create an account.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "source": {
        "type": "string",
        "description": "Optional UTM source/campaign label for attribution."
      }
    },
    "additionalProperties": false
  },
  "annotations": {}
}

Findings

Shared experience

100 / 100 · weight 30

passPage experience

weight 20

The page a person sees holds up next to the agent surface: a working interface, visible actions, readable content, nothing in the way.

passHuman parity

weight 10

The person co-browsing can see and use this page - the same page the agent's tools act on.

Task completion

47 / 100 · weight 25

failTool selection

weight 15

An agent chose an existing tool and built a schema-valid call that held up on 1 of 3 canonical intents; on "Read that page to me." no tool on the page served it. Nothing was executed, so this verifies selection, not outcomes.

warningCoverage vs. site type

weight 10

The tool set covers 2 of the 3 things an agent needs on a docs site; it cannot navigate the documentation tree.

Tool quality

92 / 100 · weight 25

passRegistration timing

weight 1

Every measured tool registered within 906ms of navigation.

toolopen_pricing

passCanonical entry point

weight 3

All 6 tools register on the canonical document.modelContext entry point.

passSchema validity

weight 4

All 6 declared input schemas are structurally valid object schemas.

warningSchema quality

weight 4

2 of 6 tool schemas are harder for an agent to use than they need to be: start_signup declares no required list, so an agent cannot tell which parameters are mandatory.

toolstart_signup

start_signup: declares no required list, so an agent cannot tell which parameters are mandatory; open_product_page: 1 parameter has no description (product)

fix

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

warningNaming quality

weight 2

Tool naming makes selection harder than it needs to be: 4 names do not start with a verb (request_demo).

toolrequest_demo

fix

{ name: "request_demo" /* short, unique, verb-based */ }

passStub detection

weight 4

All 6 tools declare an execute handler.

passRegistration errors

weight 2

No tool registration threw during the capture.

passDescription quality

weight 5

All 6 rated tool descriptions say what the tool does, when to use it, and what it returns.

Trust

0 / 100 · weight 20

failAnnotations present

weight 6

1 of 1 read-shaped tools do not declare readOnlyHint: true, so an agent has to treat them as possible writes and ask before calling. (Declaring readOnlyHint: false earns nothing - it is the default.)

toolsearch_docs

search_docs

fix

{
  name: "search_docs",
  // Declare readOnlyHint: true on tools that truly have no side effects -
  // that is the claim that lets an agent relax confirmation on reads.
  // (false is the default, so declaring it adds no information.)
  annotations: { readOnlyHint: true }
}

not applicableAnnotation mismatch

weight 6

No tool declares a readOnlyHint, so there is no safety claim to contradict.

not applicableUntrusted content hint

weight 4

No tool's contract suggests it returns text written by somebody other than the site, so there is nothing to flag as untrusted.

not applicableInjection surface

weight 4

No tool's metadata carries instruction-shaped text aimed at the agent reading it. This check only ever flags; it never credits a site.

Tool selection

33% across 3 intents

Find the page that explains authentication.ok

chosesearch_docsexpected docs searchkind matched

arguments

{
  "query": "authentication"
}

Read that page to me.missed

choseno toolexpected page readkind not applicable

No tool was picked for this intent.

arguments

{}

What other pages are in the same section?missed

choseno toolexpected navigationkind not applicable

No tool was picked for this intent.

arguments

{}

model: gemini-2.5-flash

Add the tools this site is missing

Our scanner reads your website and suggests the right WebMCP tools for it.

The open source webmcp plugin teaches your coding agent to audit a site, implement tools on document.modelContext, and verify them in a real browser. npx @ora-ai/webmcp-verify runs the verification on its own. No signup, no hosted service.

how this was captured

observed via: capture shim (Chromium 148.0.7778.96)
chrome: 148.0.7778.96
capture shim: v1
spec snapshot: 2026-08-26
mode: fast
pages: 1 - entry page only
tools: 6
run time: 14s
finished: Sep 1, 2026

Checked the way in-browser agents discover tools: the top-level document's modelContext registry, read after the page settles.

Listed in the community directory.