WebMCP Ready checks a public web page and tells you whether browser agents can call named tools on it. You get a score, a ready/not-ready verdict, every tool found, and a short list of what to fix.
Agents otherwise click around the page and guess. A ready page names the action, describes the inputs, and keeps the work on the visible page so a person can still see what happened.
What you can do
- check_page — score any public URL for WebMCP readiness
- List tools registered in JavaScript on the page
- List tools declared on HTML forms
- Flag a missing trial token, a blocked permissions policy, or origin isolation turned off
- Get the highest-impact fixes first
Who it's for
Product and engineering teams who want agents to complete booking, checkout, or support tasks on their site. Anyone comparing a live page with the WebMCP spec before a launch.
How to use it
- Call check_page with the full page URL, including https
- Read the verdict first — ready, partial, not ready, or blocked
- Review the tools list for names, descriptions, and missing fields
- Work the fix list from the top. A blocked setting means no tool can run.
Getting started
No setup needed. Pass any public page URL to check_page.
