WebMCP checker
Inspect a public page for WebMCP tools and annotated forms. Review the tool names, descriptions, and input definitions.
How the check works
Open the page in an isolated browser with WebMCP enabled when supported. Read tools exposed by the native API and inspect annotated forms. Never invoke discovered tools. If browser inspection is unavailable, return a clearly marked initial-HTML check.
- Results describe one anonymous browser session. Tools can depend on login, page state, browser support, or user interaction.
- The inspection blocks non-GET network requests and some resources. This can affect sites that need those requests to register tools. No tool execution is tested.
Read the result, then take action.
Illustrative example — not a live result
A tool has no description
The browser exposes a tool named search_docs without a description.
Next step: Add a short description that explains when an agent should call the tool and what it returns.
Common questions
Does this checker run my tools?
No. It reads registrations and form annotations. It does not invoke a tool or submit a form. Loading the page runs its normal JavaScript.
Why were no tools detected?
The page may not expose WebMCP tools in this browser session. A tool can also require login, another page state, or a different browser version. A negative result is not proof that the site has no tools.
Use this tool with an agent
Open this page in a WebMCP-compatible browser. Ask your agent to check your URL. The result appears here and is returned to the agent as JSON. Your agent can also use the public POST endpoint.
check_webmcp({ "url": "https://example.com" })
POST /api/free-tools/webmcp-checker
Content-Type: application/json
{ "url": "https://example.com" }Results contain findings, evidence, suggested fixes, a check time, and coverage limits. View the tool catalog.