Evaluation type Beta, Early Preview

WebMCP Readiness

Inspects the current evidence that a website exposes structured tools for browser agents. Absence is not a current failure, and presence is not a security certification.

Run the WebMCP Readiness Check All evaluation types

Does this website expose structured, safe actions a browser agent could use?

What WebMCP is, honestly

WebMCP is proposed and evolving.
It is not a W3C Standard.
WebMCP is not the same as server side MCP.
Declarative and imperative surfaces both exist.
Runtime registration may not be detectable by static HTML inspection.
Browser support may change.
Absence of a surface is not a current website failure.
Presence of a surface is not a security certification.
Human control, authorization, and privacy matter, and are part of what a readiness check should look for.
Every date, browser version, API name, and origin trial statement must be verified at the time it is read.

Primary sources: the official Chrome for Developers documentation and the W3C Web Machine Learning Community Group draft. This page states no specific browser version, because a version stated today is stale tomorrow.

Purpose

Inspects the current evidence that a website exposes structured tools for browser agents. Absence is not a current failure, and presence is not a security certification.

How it runs

Inputs	A public URL, inspected for declarative WebMCP tool surfaces in the served HTML.
Retrieval method	The engine performs a static inspection of the HTML the site serves, looking for declared agent tool surfaces. Runtime, script registered, and imperative surfaces may not be visible to a static inspection, and the result says so.
Observable signals	Presence of declared tool surfaces in the served HTML, Shape and labeling of any declared actions, Signals of human control, authorization, and scope on those actions.
Weighting	WebMCP Readiness reports a status and the evidence for it. It is not a maturity score, and no weighting is claimed that the evidence does not support. See the live methodology on AIOInsights.
Not applicable logic	A site that exposes no declarative surface is reported as no current evidence, which is not the same as a failure.
Failure states	An unreachable page produces a stated failure. A page inspected without finding a surface reports exactly that.
Evidence shown	The finding shows what was and was not observed in the served HTML.
Result	A WebMCP Readiness status with its evidence, not a maturity score.
Version	Engine v2.4.0. Change history.
Data retention	Handled under the AIOInsights privacy policy. AIOInsights privacy.
Security and abuse controls	The same request guard and no-execution rules as every AIOTruth type. Rate limited.

Known limitations

WebMCP is proposed and evolving. It is not a W3C Standard.
WebMCP is not the same as server side MCP.
Static inspection cannot detect runtime or script registered tool surfaces.
Browser support may change, and every browser version, API name, and origin trial claim must be verified at the time it is read.

What this does not measure

It does not measure runtime compatibility when only static HTML was inspected, it does not certify security, absence is not a current failure, and presence is not a security certification.

Run it

The WebMCP Readiness evaluation runs on AIOInsights as the WebMCP Readiness Check. When it surfaces work that needs doing, Digilu implements it.