A WebMCP tools
40 points
- Tools exposed to agents
- Imperative registration conforms to the spec
- Declarative tool forms
Free WebMCP readiness check
Scan any page: we render it in a real browser, capture every WebMCP tool it registers, validate schemas and annotations, and audit the security headers and discovery files agents rely on. You get a shareable report with a score, a grade and fixes you can paste.
Try it on this site — or read a full description of every check.
18 scored checks in four categories, plus observations. Every result shows its evidence.
40 points
20 points
20 points
20 points
Pages are rendered in headless Chromium (Cloudflare Browser Run). Tools registered by scripts, frameworks or after load are captured with their full schema and timing.
Names, descriptions and duplicates are judged with the registration rules of the current W3C draft; annotations are compared with what each tool's verb implies; schemas are checked property by property.
Prompt-injection indicators in descriptions, sensitive parameters, CSP, HSTS, mixed content and the tools Permissions-Policy that can silently switch WebMCP off.
Every lost point comes with an explanation, a snippet adapted to your page and the reference to read.
A report link to share for one hour, a JSON version of every report and a documented API.
Open your tools in the WebMCP Explorer Chrome extension to run them, record timelines and review their security.
2026-09-02
WebMCP on static sites: declarative form attributes, a fifteen-line registerTool script over a Hugo JSON index, origin-trial token placement on CDNs, and the MCP-tier boundary.
2026-09-02
WebMCP for MediaWiki: Action API modules as read tools, token discipline as the confirmation boundary, a gadget registration pattern, and the edit-authority line wikis won’t cross.
2026-09-02
A Wagtail WebMCP pattern: Python decides tool registration via before_serve_page, FormPage inherits declarative tools, json_script seeds safely, and permissions stay Django’s.
2026-09-02
WebMCP for Directus: custom endpoints with req.accountability passthrough, flow-trigger writes, the role-matrix test, and why Data Studio sessions should stay out of the agent lane.
2026-09-02
WebMCP for Ghost themes: annotated search forms, {{#get}}-seeded tools, a routes.yaml agents.json endpoint, the Portal caveat, and how the member tier keeps entitlements honest.
2026-09-02
A WebMCP guide for Strapi: why tools live in the front end, Nuxt and Astro registration, the same-origin proxy as privilege boundary, and one registry feeding browser and MCP tiers.
WebMCP is a browser API, drafted at the W3C Web Machine Learning Community Group with Chrome as first implementer, that lets a web page register "tools" — functions with a name, a description and a JSON input schema — which AI agents in the browser can call instead of clicking around the page.
It loads your page in a real headless Chromium with a recording script installed before your code runs. When the browser has WebMCP enabled the native API is wrapped; otherwise a stand-in that applies the specification rules records each registerTool() call. Declarative forms are read from the rendered DOM. Tools are never executed.
Yes. Scans are free and need no account. Fair-use limits apply per visitor to keep the shared browser capacity available to everyone.
Only the scanned address (origin and path — query strings are dropped) and the report, for one hour at most: the report is deleted when you close it. No account, no cookie, no IP address with reports. See the privacy page.
Yes: the report still checks HTTPS, CSP, Permissions-Policy, structured data, llms.txt, Open Graph and robots.txt, and gives copy-paste code to register your first tool.
No. It is our own transparent heuristic (ruleset 2026-10-21), published in full on the scoring page. It is not a certification and not a search ranking factor.