The short answer: WebMCP is the part of agent commerce your customers' browser will handle — and UCP is the part that actually completes the sale. If you want to know whether your store is ready for the agents arriving through both, enter your domain here. It checks the commerce layer — the half that decides whether an agent can finish a checkout, not just start one.
The longer answer — what "WebMCP and UCP ready" actually means for a store, how the two fit together, and what to do about it — is what this post covers.
What "WebMCP-ready" actually means
WebMCP (the Web Model Context Protocol) is a W3C Community Group draft from Google and Microsoft engineers that landed in February 2026 and shipped as an early preview in Chrome 146. It adds a browser-native API — navigator.modelContext — that lets a web page hand an in-browser AI agent a set of structured, callable tools instead of forcing it to scrape the DOM.
In plain commerce terms: your search box, your filter panel, your add-to-cart button, and your checkout form stop being pixels an agent has to guess at, and become named tools the agent can call directly. There are two ways to expose them:
