shivanshutiwari.in WebMCP audit

Name: shivanshutiwari.in WebMCP audit
Creator: ora

Rescan

audited Sep 2, 2026in 12s

81/ 100100% of the applicable check weight evaluated

4 tools registered. Strongest in shared experience, weakest in task completion.

Shared experience100

Task completion40

Tool quality100

Trust80

https://shivanshutiwari.in

Tools

4 read, 0 write

Loading map

get_contact_info

Returns Shivanshu Tiwari's public contact information: email address, GitHub profile, LinkedIn profile, and contact form URL. Read-only lookup — it does not send messages or modify anything.Answers a question. Declared read only.

pagehttps://shivanshutiwari.in/

implementation

viaimperative

entry pointdocument

registered after264ms

executepresent

api surfaceTakes no parameters.

annotations

read onlytrue

untrusted contenttrue

titlenot declared

0 findingsNo check named this tool.

tool json

{
  "name": "get_contact_info",
  "description": "Returns Shivanshu Tiwari's public contact information: email address, GitHub profile, LinkedIn profile, and contact form URL. Read-only lookup — it does not send messages or modify anything.",
  "inputSchema": {
    "type": "object",
    "properties": {}
  },
  "annotations": {
    "readOnlyHint": true,
    "untrustedContentHint": true
  }
}

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

40 / 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 "Show me everything on that record." 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 4 things an agent needs on a saas site; it cannot create a record or start a job or update or move an existing record.

Tool quality

100 / 100 · weight 25

passRegistration timing

weight 1

Every measured tool registered within 265ms of navigation.

toolget_project_details

passCanonical entry point

weight 3

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

passSchema validity

weight 4

All 4 declared input schemas are structurally valid object schemas.

passSchema quality

weight 4

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

passNaming quality

weight 2

All 4 tool names are consistent, verb-led, and within Chrome's size guidance.

passStub detection

weight 4

All 4 tools declare an execute handler.

passRegistration errors

weight 2

No tool registration threw during the capture.

passDescription quality

weight 5

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

Trust

80 / 100 · weight 20

passAnnotations present

weight 6

All 4 read-shaped tools declare readOnlyHint: true - the one declared claim that lets an agent treat a call as safe to make without asking.

passAnnotation mismatch

weight 6

No tool claims to be read-only while its own name or description says it writes (4 declared hints checked).

passUntrusted content hint

weight 4

All 1 tool that looks like it returns third-party text declares untrustedContentHint.

warningInjection surface

weight 4

1 of 4 tools carry instruction-shaped text in their own metadata: get_project_details description instructs agent to use tool after another specific tool.

toolget_project_details

get_project_details: description instructs agent to use tool after another specific tool

fix

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

33% across 3 intents

Find the record for a company called Northwind.ok

chosesearch_portfolio_projectsexpected record searchkind matched

arguments

{
  "query": "Northwind"
}

Show me everything on that record.missed

choseno toolexpected record detailkind not applicable

No tool was picked for this intent.

arguments

{}

Create a new contact called Dana Reeve.missed

choseno toolexpected record createkind 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: v2
spec snapshot: 2026-08-26
mode: fast
pages: 1 - entry page only
tools: 4
run time: 12s
finished: Sep 2, 2026

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