marketresearchfuture.com WebMCP audit

Name: marketresearchfuture.com WebMCP audit
Creator: ora

Rescan

audited Aug 28, 2026in 7s

48/ 100

4 tools registered. Strongest in usefulness, weakest in human experience.

WebMCP use43

Usefulness88

Human experience0

about:blank

No agent run recorded yet.

No steps recorded

Tools

search_reports

Search for market research reports on MRFR by keyword or industry.Takes an action on the site.

pagehttps://www.marketresearchfuture.com/

implementation

viaimperative

entry pointnavigator

registered after1347ms

executepresent

api surfaceTakes no parameters.

annotations

read onlynot declared

destructivenot declared

idempotentnot declared

open worldnot declared

untrusted contentnot declared

titlenot declared

4 findings

failCanonical entry point

0 / 4

Every tool registers through the deprecated navigator.modelContext alias; move them to document.modelContext before the alias is removed.

fix

// Use the canonical entry point - navigator.modelContext is deprecated.
document.modelContext.provideContext({ tools: [/* ... */] });

failSchema validity

0 / 5

4 of 4 tools declare an input schema an agent cannot read: search_reports declares no input schema.

search_reports: declares no input schema; view_report: declares no input schema; list_categories: declares no input schema; request_sample: declares no input schema

fix

{
  name: "search_reports",
  inputSchema: { type: "object", properties: { /* ... */ }, required: [] }
}

failAnnotations present

0 / 4

4 of 4 tools declare no readOnlyHint, so an agent cannot tell a read from a write without guessing from the name.

search_reports, view_report, list_categories, request_sample

fix

{
  name: "search_reports",
  annotations: { readOnlyHint: true, destructiveHint: false, idempotentHint: true }
}

warningHuman parity

0 / 8

4 of 4 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.

search_reports, view_report, list_categories, request_sample

fix

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

tool json

{
  "name": "search_reports",
  "description": "Search for market research reports on MRFR by keyword or industry.",
  "inputSchema": null,
  "annotations": {}
}

Findings

WebMCP use

43 / 100 · weight 50

passTools registered

4 / 4

4 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.

warningRegistration timing

2 / 4

The slowest tool took 1347.4000000953674ms to register, past the 1000ms an agent reading the registry at first paint would wait for.

toolrequest_sample

request_sample: registered at 1347.4000000953674ms

fix

// Register tools as soon as they're ready, not behind a deferred/async chunk.
document.modelContext.provideContext({ tools: [/* ... */] });

failCanonical entry point

0 / 4

Every tool registers through the deprecated navigator.modelContext alias; move them to document.modelContext before the alias is removed.

toolsearch_reports

fix

// Use the canonical entry point - navigator.modelContext is deprecated.
document.modelContext.provideContext({ tools: [/* ... */] });

failSchema validity

0 / 5

4 of 4 tools declare an input schema an agent cannot read: search_reports declares no input schema.

toolsearch_reports

search_reports: declares no input schema; view_report: declares no input schema; list_categories: declares no input schema; request_sample: declares no input schema

fix

{
  name: "search_reports",
  inputSchema: { type: "object", properties: { /* ... */ }, required: [] }
}

passSchema quality

4 / 4

All 4 tool schemas describe their parameters and stay within Chrome's size guidance.

passStub detection

5 / 5

All 4 tools declare an execute handler.

failAnnotations present

0 / 4

4 of 4 tools declare no readOnlyHint, so an agent cannot tell a read from a write without guessing from the name.

toolsearch_reports

search_reports, view_report, list_categories, request_sample

fix

{
  name: "search_reports",
  annotations: { readOnlyHint: true, destructiveHint: false, idempotentHint: true }
}

not applicableAnnotation mismatch

0 / 3

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

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

4 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

88 / 100 · weight 30

warningNaming quality

1.8 / 2

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

toolrequest_sample

fix

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

toolsearch_reports

search_reports, view_report, list_categories, request_sample

fix

<!-- Give the tool a visible counterpart: a declarative form is one the person can see and use too. -->
<form toolname="search_reports" 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: 4
run time: 7s
finished: Aug 28, 2026