ainative.studio WebMCP audit

Rescan
audited Oct 24, 2026in 10s
53/ 100Incomplete audit · 47% of the applicable check weight evaluated

3 tools registered. Strongest in tool quality, weakest in trust. Tool selection was not measured.

Shared experience50
Tool selectionN/A
Tool quality100
Trust0
https://ainative.studio
Captured view of https://ainative.studio

Tools

0 read, 0 write, 3 undeclared
Loading map
search_site: fail

search_site

Search AINative Studio’s blog posts, tutorials, showcases, and resources using the site’s real semantic search. Returns titles, URLs, and descriptions of matching content.No behaviour hints declared. Agents should treat it as possibly state-changing.
pagehttps://ainative.studio/
implementation
viaimperative
entry pointdocument
registered after921ms
executepresent
api surface
queryrequired
contentTypeoptional
limitoptional
annotations
read onlynot declared
untrusted contentnot declared
titlenot declared
2 findings
failAnnotations present
weight 4
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_site, get_pricing
fix
{
  name: "search_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 }
}
warningHuman parity
weight 8
3 tools run through the JavaScript API and the page itself was not graded on this run, so parity could not be confirmed. A visible effect in your existing UI when a tool runs closes the gap.
search_site, get_pricing, start_signup
fix
// Make the tool's effect visible on the page the person is looking at:
// update the same UI your existing human flow uses when search_site runs,
// so the person co-browsing sees what the agent just did.
execute: async (args, { signal }) => {
  const result = await performAction(args, signal);
  renderResultInPage(result); // the human-visible half of the same action
  return result;
}
tool json
{
  "name": "search_site",
  "description": "Search AINative Studio’s blog posts, tutorials, showcases, and resources using the site’s real semantic search. Returns titles, URLs, and descriptions of matching content.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "query": {
        "type": "string",
        "description": "Search keywords, e.g. \"vector database\" or \"MCP server hosting\"."
      },
      "contentType": {
        "type": "string",
        "enum": [
          "all",
          "blog_post",
          "tutorial",
          "showcase",
          "resource"
        ],
        "description": "Optional filter to a single content type. Defaults to all content types."
      },
      "limit": {
        "type": "number",
        "description": "Maximum number of results to return (default 10, max 20)."
      }
    },
    "required": [
      "query"
    ]
  },
  "annotations": {}
}
Showing search_site

Findings

Shared experience

50 / 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 and not consequentialHint: true.
not measuredPage experience
weight 16
The page-experience model hop returned no usable result, so the page was not graded.
warningHuman parity
weight 8
3 tools run through the JavaScript API and the page itself was not graded on this run, so parity could not be confirmed. A visible effect in your existing UI when a tool runs closes the gap.
toolsearch_site
search_site, get_pricing, start_signup
fix
// Make the tool's effect visible on the page the person is looking at:
// update the same UI your existing human flow uses when search_site runs,
// so the person co-browsing sees what the agent just did.
execute: async (args, { signal }) => {
  const result = await performAction(args, signal);
  renderResultInPage(result); // the human-visible half of the same action
  return result;
}

Tool selection

not measured
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 and not consequentialHint: true.
not measuredTool selection
weight 12
The tool-selection model hop returned no usable result.
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

100 / 100 · weight 25
passRegistration timing
weight 1
Every measured tool registered within 927ms of navigation.
toolstart_signup
passCanonical entry point
weight 3
All 3 tools register on the canonical document.modelContext entry point.
passSchema validity
weight 4
All 3 declared input schemas are structurally valid object schemas.
passSchema quality
weight 4
All 3 tool schemas describe their parameters, and every description stays within Chrome's size guidance.
passNaming quality
weight 2
All 3 tool names are consistent, verb-led, and within Chrome's size guidance.
passStub detection
weight 4
All 3 tools declare an execute handler.
passRegistration errors
weight 2
No tool registration threw during the capture.
not measuredDescription quality
weight 5
The description-quality model hop returned no usable result, so descriptions were not rated.

Trust

0 / 100 · weight 20
failAnnotations present
weight 4
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_site
search_site, get_pricing
fix
{
  name: "search_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 4
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 applicableConsequential hint
weight 3
No tool name reads like a consequential action (a purchase, a booking, a payment, a transfer, a deletion), so there is no consequentialHint to expect.
not applicableHint vs. observed
weight 3
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 and not consequentialHint: true.
not measuredInjection surface
weight 3
The injection-surface model hop returned no usable result, so tool contracts were not reviewed for injection surface.

Tool selection

The tool-selection model hop returned no usable result.

Add the tools this site is missing

Our scanner reads your website and suggests the right WebMCP tools for it.
Reads the site's public pages; takes a few seconds.
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-10-16
mode
fast
pages
1 - entry page only
tools
3
invoked
not invoked; a live audit calls them
run time
10s
finished
Oct 24, 2026
Checked the way in-browser agents discover tools: the top-level document's modelContext registry, read after the page settles.