agentspeed.
Rubric / Actionability

WebMCP actions

actionability.web_mcp
weight 1deterministicemerging

The page exposes WebMCP (in-browser Model Context Protocol) so on-page agents can invoke tools without leaving the tab.

Adoption of what this check tests is still climbing, so failing it is an opportunity rather than a defect. Remediation lists rank these after established fixes, and the weight moves only when measurement earns it.

Definition
Check ID
actionability.web_mcp
Category
Actionability
Weight
1
Counts toward the score
Yes.
Evaluated by
A fixed rule with no threshold of our choosing. The same input always produces the same verdict.
Standard maturity
emerging
Canonical spec
None. This check has no published external specification — it is an AgentSpeed rule.
Introduced in
r2026.04.2
Retired in
Still active.
History
Every change to the instrument— including the versions that changed this check
Machine-readable
/rubric.json— this check, and every other, as data
How often this check is right

No rate published. Too few labelled cases to publish a rate: 1 flagged case (30 needed to publish), 1 defective case (30 needed to publish). The counts are the honest answer here. The matrix behind actionability.web_mcp is 2 labelled cases — reported here rather than turned into a percentage that would read as more certain than the evidence is.

Corpus v1, measured under rubric r2026.11.0. Full method and every other check at /rubric/accuracy.

How to fix it
Embed a WebMCP server on pages that have first-class actions (cart, support form, account settings). Agents in browser sessions invoke these directly without DOM scraping.
Does your site pass this check?

Free scan, 30 seconds, no signup — this check and the other 35, with the exact evidence for each verdict.

Scan my site →
WebMCP actions · actionability.web_mcp · AgentSpeed