What is WebMCP, and can a page offer tools to AI agents?
WebMCP is an experimental browser feature that lets a page tell an AI agent what it can do, such as search or book, instead of leaving the agent to work out which buttons to press. A form can declare itself a tool in the HTML. We look for those declarations in the page, and only those.
What it actually is
Today a browsing agent looks at a page the way a person would and guesses. WebMCP lets the page say it directly: this form is a tool named "search flights", and here is what it does. The W3C community group's draft specifies a script route, where the page registers tools while it runs. Chrome's experimental declarative form goes further: a form carries a tool name and a tool description in its markup. Some CDNs also inject a bridge script. All of it is a draft, not a standard.
Why it matters
An agent that can call a page's real actions is more reliable than one clicking at guesses, and a site that offers them controls what the agent does on it. If the feature matures, declaring tools becomes the way a site makes its actions usable to agents.
What good looks like
Forms that carry both a tool name and a tool description, so the browser registers them, or a bridge script that exposes the page's tools. A name with no description is not a registered tool, and we do not count it. The tools should match what the form actually does.
Being honest about it
This is the most experimental signal we check. It is a draft, it ships in a browser as a trial, and most sites have nothing here. It never fails a page and stays out of the headline score. One limit matters: we read only what is in the page itself, so tools a script registers while it runs are invisible to us and a warning does not mean there are none. We used to say we do not check for WebMCP; since the static signals can be read, we do.
Where most sites go wrong
A form with a tool name and no description looks registered and is not. A tool registered only inside a script bundle is real but invisible from outside. And a tool description that promises something the form does not do sends agents to the wrong action.
On the web
In October 2026, 1% of the sites we scanned passed the “WebMCP tools in the page” check.
| Result | Share of sites |
|---|---|
| Pass | 1% |
| Worth a look | 99% |
| To fix | 0% |
| Couldn't judge | <1% |
Next.js sites pass it most often, at 1%. WordPress sites pass it least often, at 0%.
Not enough history yet.
Based on the sites Bot Appétit has scanned: ones people chose to scan, plus lists we scan for research. Not a random sample of the web.
Not sure where yours stands?
A free scan checks this and everything else in about 20 seconds — no signup. Or if it's already flagged and you'd rather it were simply handled, we do that too.
Flagged for this one? We handle it. No pitch, just a plain-English chat.
Book a call