Enter your site and we fetch it live, looking for the two WebMCP surfaces. You get an honest verdict in seconds. Almost no site has this yet, so a clean “not yet” is expected.
AIOInsights
WebMCP Readiness is an AIOTruth evaluation type, delivered through AIOInsights.
Is your site ready for AI agents?
WebMCP is a proposed browser standard in early development. It would let a site hand an AI agent a menu of callable tools instead of making the agent reverse-engineer the interface: read the screen, hunt for a button, and hope the click did what it expected.
This check looks for current evidence that a site exposes structured tools for AI agents. Absence does not mean the site is defective, and support is not yet universal. It performs static inspection of your homepage HTML and inline scripts; it does not execute JavaScript, so it cannot confirm tools registered at runtime.
Today: the agent guesses
An AI agent lands on your page and has to figure it out like a person would: read the screen, hunt for the right button, and hope the click does what it expected. Slow, brittle, and often wrong.
With WebMCP: you hand it the menu
Your site declares its actions as callable tools: get a quote, check availability, start a booking. The agent calls the tool directly, with the inputs it needs. No guessing, no screenshotting.
What WebMCP actually is
WebMCP is a proposed browser API, document.modelContext (originally navigator.modelContext, moved in July 2026), that would let a website expose its own features to AI agents as structured, callable tools. It was authored by engineers at Google and Microsoft through the W3C Web Machine Learning Community Group, announced in February 2026, and opened a public origin trial in Chrome 149 that runs through Chrome 156. It is described in a Community Group draft, not a W3C Standard, and is not on the W3C Standards Track. It is one of several proposals for a business-to-agent interface for the agentic web.
Why this is not just another llms.txt
They solve different problems. One helps AI read you. The other lets an agent act on your site. That difference is why WebMCP has momentum where llms.txt stalled.
| llms.txt | WebMCP | |
|---|---|---|
| What it is | A static text file at your root | A live browser API your site calls |
| What it does | Hints to AI what your content means | Publishes actions an agent can invoke |
| Read or act | Read only | Act: quote, search, book, submit |
| Adoption | Years old, largely unused by AI systems | Backed by Google + Microsoft, in Chrome origin trial |
“I like the WebMCP approach, as well as the commerce integrations: they have clear goals and processes.”
John Mueller, Google, who separately called llms.txt “purely speculative for now.”Honest status: WebMCP is in a public origin trial, not a finished standard. It is available to test through the origin trial in Chrome (Chrome 149 through 156) and has experimental support in Edge behind a flag; it is not yet supported across all browsers. We are telling you this because being early is the point: you can understand it before it settles, without betting anything on a timeline nobody can promise.
Discuss Agent Readiness with Digilu
This check tells you what evidence your site currently publishes. What to do about it depends on your business and on how the standard develops. WebMCP is in origin trial, browser support is not settled, and we are not going to sell you an implementation as a finished managed service while that is true. What we will do is look at your situation with you and say plainly whether it is worth acting on yet.
Discuss Agent Readiness with DigiluBeta 0.1 · Found a problem or think we got something wrong? Help us make this better.
Two levels of responsibility.
Agent-readiness standards and website implementations continue to evolve after a one-time check.
You can handle the recommendations yourself, have Digilu keep watching for changes, or have Digilu maintain the supported foundation. Nothing here expires and nothing changes if you do nothing.
We keep the foundation right.
Digilu brings your business into The Observatory, keeps watching the supported signals, and handles the supported maintenance of the website and core digital foundation.
- Continuous observation and meaningful-change alerts
- Digilu maintains the website and core digital foundation
- Entity details kept consistent across the sources you appear on
- Monthly Mission Briefing covering what changed and what Digilu completed
Secure Stripe checkout. Automated onboarding. Cancel any month.
Have Digilu manage your reputation
We manage your reputation and what happens after the sale.
Everything in Trust Foundation, and Digilu also manages your Google Business Profile, the reputation channels that decide whether people choose you, and the retention, referral and advocacy work after a customer buys.
- Everything in Trust Foundation
- Google Business Profile management
- Reputation-channel management and review stewardship
- Retention, referral and advocacy after the first sale
Secure Stripe checkout. Automated onboarding. Cancel any month.
Trust Foundation carries the observation and the supported maintenance of the website and core digital foundation. Adaptive Management carries all of that and additionally manages the Google Business Profile, the reputation channels that decide whether you are chosen, and the relationship after the first sale.
A result tells you where you stand. Digilu takes responsibility from there.
AIOInsights evaluates the public signals as they are today. The Observatory keeps watching them. Digilu carries the level of responsibility you choose, and no more than that.
Adaptive Management: We manage your reputation and what happens after the sale. · Trust Foundation: We keep the foundation right.
Check another part of the picture.
WebMCP Readiness Check covers one dimension. These evaluate the others.