Is this site WebMCP-ready?
WebMCP lets a page hand an AI agent real tools instead of making it guess at your DOM — but it only works behind a Chrome origin-trial token, and an expired token fails silently. Decode the token, read the expiry, and see what registration code the page actually serves.
Data API
Check WebMCP support at scale
The same check is an API call and an MCP tool your AI agent can use, on one key. The first 1,000 credits every month are free, no card needed.
WebMCP check
2 credits per callWhether a site exposes in-page tools to browser agents (WebMCP).
GET/api/hub/v1/sites/{domain}/webmcp
curl https://businessmcp.com/api/hub/v1/sites/acme.com/webmcp \
-H "Authorization: Bearer $BUSINESSMCP_API_KEY"MCP tool webmcp_check · full reference
What we can and cannot see
We fetch the page and read the HTML it serves. We do not run its JavaScript, so tools registered from an external bundle do not show up here — and a blank result means “not in the HTML we fetched”, never “this site has no WebMCP”. The token is the part we can be precise about: it carries its own feature name, origin and expiry, so we decode and print them rather than guessing.
If you are wiring this up yourself, the WebMCP guide has the exact code, the two API locations you need to read during the Chrome 150 transition, and an honest read on who is calling these tools today.
Frequently asked questions
What does this actually check?
Three things in the HTML the site serves: any <meta http-equiv="origin-trial"> token (and the Origin-Trial response header), which we decode to read the feature name and expiry date; whether the page references document.modelContext or the deprecated navigator.modelContext; and whether registerTool( appears anywhere in the markup.
Why does it say "not in HTML" for a site I know has WebMCP?
Because we read the served HTML and do not execute the page’s JavaScript the way Chrome does. If the registration lives in an external bundle — which is normal — it is invisible to a fetch. That is why the result separates "we found nothing" from "this site has no WebMCP": only the first is something we can honestly claim.
My token decodes but the tools still do nothing.
Check the expiry we print. An expired origin-trial token fails silently: document.modelContext simply goes back to undefined, every registerTool() call becomes a no-op, and nothing is logged. Also check the origin on the token matches the origin serving the page — a token issued for www.example.com does not cover example.com unless it was issued with subdomain matching.
When does the WebMCP origin trial end?
The Chrome trial runs from Chrome 149 to 156 and ends on 16 November 2026. After that, unless Chrome ships the API by default or extends the trial, tokens stop working and registered tools stop being visible.
Is anything actually calling these tools yet?
Barely. No mainstream agent client consumes WebMCP tools in production today — Gemini in Chrome is announced as the first — and checker tools currently outnumber known implementations. Shipping WebMCP is cheap insurance for the agents arriving, not a source of traffic this quarter. Our WebMCP guide says more about that.