Paste a URL and see whether its HTML declares WebMCP tools: form tools, inline registerTool() calls, the origin-trial token and outdated names. Plus llms.txt, AI bot rules and JSON-LD.
A static check of your server's HTML. The render scan is AI Agent Readiness.
AI Rankiabook_table_le_petit_bistrouser presses SubmitInitiates a dining reservation request at Le Petit Bistro. Accepts customer details, timing, and seating preferences.
namephonedatetimeguestsseatingrequests7 of 7 parameters described with toolparamdescription
googlechromelabs.github.io.We read the HTML your server sends for this URL, plus /robots.txt and /llms.txt on the same host. We don't run or download your JavaScript files.
Read that day in the spec repository, Chromium's source and Chrome's documentation. The checker uses these names.
With a desktop Chrome User-Agent. Redirects only within the same site, up to 3. At most 10 seconds and 1.5 MB.
Forms with toolname, inline scripts calling registerTool(), WebMCP libraries, and origin-trial tokens from the meta tag or the Origin-Trial header, decoded.
/robots.txt and /llms.txt on the same host (6 seconds, 256 KB each) and the JSON-LD in the HTML. Fixed rules, no AI.
It only covers the HTML your server sent. Everything a script adds later is out of its sight.
toolname and tooldescription, or an inline script calling document.modelContext.registerTool().registerTool() without document.modelContext, but no complete tool. The result lists what's missing.A tool is a name, a description and an input schema. WebMCP is a browser API drafted by the W3C Web Machine Learning Community Group: a page registers named tools, and an AI agent in the browser calls them instead of clicking through the interface. It's a draft, not a W3C standard.
document.modelContext.registerTool(), the part in the spectoolname and tooldescription on a form; out of the spec since Oct 8, 2026, still in Chrome<!-- Turns the API on in Chrome 149-162 -->
<meta http-equiv="origin-trial"
content="YOUR_WEBMCP_TOKEN">
<script>
document.modelContext?.registerTool({
name: "search_products",
description: "Search products by keyword",
inputSchema: {
type: "object",
properties: {
query: { type: "string" },
},
required: ["query"],
},
annotations: { readOnlyHint: true },
execute: async ({ query }) => {
const res = await fetch("/api/search?q="
+ encodeURIComponent(query));
return res.json();
},
});
</script><!-- Turns the API on in Chrome 149-162 -->
<meta http-equiv="origin-trial"
content="YOUR_WEBMCP_TOKEN">
<!-- Out of the spec since Oct 8, 2026; still in Chrome -->
<form toolname="search_products"
tooldescription="Search products by keyword"
action="/search">
<input name="query"
toolparamdescription="What to search for">
<button type="submit">Search</button>
</form>registerTool() returns a promise; to remove a tool, pass an AbortSignal and abort it.The AI Agent Readiness scan in the app renders your homepage in headless Chrome. A listener injected before your page's scripts records every document.modelContext.registerTool() call; then it counts the form tools on the rendered page.
getTools()await document.modelContext.getTools() in the console, or run the render scan.<meta http-equiv="origin-trial"> tag or an Origin-Trial header (Chrome 149 to 162). To test locally, turn on chrome://flags/#enable-webmcp-testing (Chrome docs, trial).AI Rankia tracks whether AI engines mention and cite your brand, and its AI Agent Readiness scan renders your homepage to find the WebMCP tools it registers.
A token isn't a tool. An origin-trial token only turns the API on in Chrome for that origin until it expires. We read its feature, origin and expiry; Chrome checks the signature.
navigator.modelContextMoved to document.modelContext; Chromium removed it too (in WPT Jul 9, 2026)May 27, 2026provideContext() · clearContext()Removed from the specMar 5, 2026unregisterTool(name)Replaced by an AbortSignal passed to registerTool()Mar 26, 2026window.agentFirst explainer, replacedOct 9, 2025tool-name · tool-descriptionNot in the spec, Chromium or Chrome's docs. We flag themn/aDates from the spec repository's history and the Chromium change list, read Oct 13, 2026. window.agent was in the first explainer (Aug 7, 2025).
This check reads the one URL you enter, over http or https on ports 80 and 443, and stops if it redirects to another domain; private and reserved addresses are blocked. The render scan reads your homepage (and, for stores, one product page).