chilipiper.com WebMCP audit

Name: chilipiper.com WebMCP audit
Creator: ora

Rescan

audited Sep 12, 2026in 12s

76/ 100100% of the applicable check weight evaluated

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

Shared experience100

Tool selection100

Tool quality86

Trust0

https://chilipiper.com

Tools

0 read, 0 write, 3 undeclared

Loading map

search_chilipiper_site

Search chilipiper.com's page index (products, solutions, pricing, integrations, customer stories, blog). Returns matching pages as markdown links with one-line descriptions.No behaviour hints declared. Agents should treat it as possibly state-changing.

pagehttps://www.chilipiper.com/

implementation

viaimperative

entry pointprovideContext

registered after748ms

executepresent

api surface

queryrequired

annotations

read onlynot declared

untrusted contentnot declared

titlenot declared

2 findings

failCanonical entry point

weight 3

Every tool uses the removed provideContext API; register each tool with document.modelContext.registerTool().

fix

// document.modelContext is the canonical entry point - the navigator.modelContext alias is deprecated.
document.modelContext.registerTool({ /* ... */ });

failAnnotations present

weight 5

2 of 2 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.)

search_chilipiper_site, get_page_as_markdown

fix

{
  name: "search_chilipiper_site",
  // 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 }
}

tool json

{
  "name": "search_chilipiper_site",
  "description": "Search chilipiper.com's page index (products, solutions, pricing, integrations, customer stories, blog). Returns matching pages as markdown links with one-line descriptions.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "query": {
        "type": "string",
        "description": "Keywords to match against page titles and descriptions"
      }
    },
    "required": [
      "query"
    ]
  },
  "annotations": {}
}

Findings

Shared experience

100 / 100 · weight 30

not applicableVisible effect

weight 6

Not invoked on this run: this audit did not call any tool. Scheduled re-audits only read the registry; a live audit from the report page calls the tools that declare readOnlyHint: true.

passPage experience

weight 16

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 8

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

Tool selection

100 / 100 · weight 25

not applicableInvoke success rate

weight 6

Not invoked on this run: this audit did not call any tool. Scheduled re-audits only read the registry; a live audit from the report page calls the tools that declare readOnlyHint: true.

passTool selection

weight 12

An agent chose an existing, callable tool and built a schema-valid call for all 3 canonical intents, each matching the kind of tool its intent needs. Nothing was executed, so this verifies selection, not outcomes.

not applicableCoverage vs. site type

weight 7

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.

Tool quality

86 / 100 · weight 25

passRegistration timing

weight 1

Every measured tool registered within 748ms of navigation.

toolopen_demo_booking

failCanonical entry point

weight 3

Every tool uses the removed provideContext API; register each tool with document.modelContext.registerTool().

toolsearch_chilipiper_site

fix

// document.modelContext is the canonical entry point - the navigator.modelContext alias is deprecated.
document.modelContext.registerTool({ /* ... */ });

passSchema validity

weight 4

All 3 declared input schemas are structurally valid object schemas.

passSchema quality

weight 4

All 2 of 3 tool schemas that declare parameters describe them (the other 1 declares no parameters), and every description stays within Chrome's size guidance.

warningNaming quality

weight 2

Tool naming makes selection harder than it needs to be: 1 name does not start with a verb (open_demo_booking).

toolopen_demo_booking

fix

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

passStub detection

weight 4

All 3 tools declare an execute handler.

passRegistration errors

weight 2

No tool registration threw during the capture.

passDescription quality

weight 5

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

Trust

0 / 100 · weight 20

failAnnotations present

weight 5

2 of 2 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_chilipiper_site

search_chilipiper_site, get_page_as_markdown

fix

{
  name: "search_chilipiper_site",
  // 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 5

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

not applicableUntrusted content hint

weight 3

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

not applicableHint vs. observed

weight 4

Not invoked on this run: this audit did not call any tool. Scheduled re-audits only read the registry; a live audit from the report page calls the tools that declare readOnlyHint: true.

warningInjection surface

weight 3

1 of 3 tools carry instruction-shaped text in their own metadata: get_page_as_markdown description instructs agent to prefer another tool.

toolget_page_as_markdown

get_page_as_markdown: description instructs agent to prefer another tool

fix

{
  name: "get_page_as_markdown",
  // Metadata DESCRIBES the tool - it never addresses the agent reading it.
  // Rewrite any name, description, title, or schema field description that
  // instructs the agent (which tool to prefer, what to output, rules to
  // ignore) so it states what the tool does and what it returns instead.
  description: "Searches the catalog and returns matching items with prices."
}

Tool selection

100% across 3 intents

I want to search chilipiper site on this site.ok

chosesearch_chilipiper_siteexpected search chilipiper sitekind matched

arguments

{
  "query": ""
}

I want to get page as markdown on this site.ok

choseget_page_as_markdownexpected get page as markdownkind matched

arguments

{
  "path": "/"
}

I want to open demo booking on this site.ok

choseopen_demo_bookingexpected open demo bookingkind matched

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 151.0.7922.34)
chrome: 151.0.7922.34
capture shim: v3
spec snapshot: 2026-08-26
mode: fast
pages: 1 - entry page only
tools: 3
invoked: not invoked; a live audit calls them
run time: 12s
finished: Sep 12, 2026

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