Agent-readiness audit
Lighthouse agentic-browsing checks (webmcp-registered-tools, form-coverage, schema-validity). We map which flows agents already fail and which tools are worth registering first.
Founder-led · Chrome origin trial live
Your site already works for humans. We add WebMCP tools so browser agents can search, book, buy, and get support — without guessing at the DOM.
The origin trial is live and Lighthouse has an agentic-browsing category — but almost nobody has shipped tools on real sites yet. That's the gap we close.
Three ways we help
Lighthouse agentic-browsing checks (webmcp-registered-tools, form-coverage, schema-validity). We map which flows agents already fail and which tools are worth registering first.
Imperative tools + declarative form coverage on your existing stack. Origin-trial token, document/navigator fallback, structured logging — no full rewrite.
Confirmation on money-moving actions, tight tool schemas, human-in-the-loop patterns. Not a chatbot widget bolted onto the corner.
Typed tools in the browser — early, but real
WebMCP is a proposed W3C Web Machine Learning CG draft (not a finished standard), co-edited by Google and Microsoft. It lets a page register typed JavaScript tools so browser AI agents can call site features instead of scraping the DOM or clicking screenshots.
The API lives on document.modelContext (moved from navigator.modelContext in the 21 Jul 2026 draft). Always feature-detect: const modelContext = document.modelContext ?? navigator.modelContext;
Browser support (Aug 2026): Chrome 149–156 origin trial (flag: enable-webmcp-testing). Edge experimental behind a flag. Firefox and Safari watching. Mainstream agents (Claude, ChatGPT Agent, Perplexity) do not consume WebMCP yet — Google has said Gemini in Chrome will. Lighthouse audits: webmcp-registered-tools, form-coverage, schema-validity.
WebMCP borrows MCP tool primitives but runs in the browser. Tools execute as the logged-in user. A site can have both a hosted MCP server (headless) and WebMCP tools (in-browser agents). This is not Anthropic MCP.
registerTool on your existing site
const modelContext =
document.modelContext ?? navigator.modelContext;
await modelContext.registerTool({
name: "search_products",
description: "Search the catalog by keyword",
inputSchema: {
type: "object",
properties: {
query: { type: "string" },
},
required: ["query"],
},
execute: async ({ query }, { signal }) => {
const results = await searchCatalog(query, { signal });
return { items: results, count: results.length };
},
});This page is the proof of work
We practice what we sell. Three tools are registered on this page right now. Use the Model Context Tool Inspector extension, or the manual buttons below when WebMCP is enabled.
This page registers real tools via document.modelContext. Try them with the Chrome flag or origin trial — not a fake chatbot.
Book a call or request an audit
WebMCP Developers is a founder-led shop by Shankhadeep Dey. No fake 50-person agency — you work directly with someone who ships WebMCP on production sites.
Or let an agent call request_audit to fill this form.