Charles Jones
WebMCP lets a web page declare tools an AI agent can call — read the services, check a date, make the booking — instead of leaving the agent to guess from rendered HTML.
Where the standard actually stands, measured 2026-08-27: accepted by the W3C WebML Community Group in September 2025; the Chrome 149 origin trial is live; native Chrome/Edge support is targeted for H2 2026. The W3C explainer is held here as first-party bytes, hash-verified — 70 quotes checked against the stored document, none failed.
Where adoption actually stands, and the correction matters: in a crawl of 27,112 business sites, WebMCP markup at the page level rounds to nothing. At the platform level it reaches 7.2% — and every instance is Wix or Shopify shipping it to the business. None of it was authored by the business. Separately, 42.8% of that fleet is agent-invisible outright — restated 2026-09-01, down from a published 47.3% that had counted sites our own crawler never reached.
So the honest position is not “everyone needs this yesterday.” It is that the platforms are quietly making their own tenants agent-ready while independent sites are not, and nobody is doing it deliberately for an independent operator. That is the work.