Free tools

Free · no account

WebMCP and agent discovery checker

Check the protocols AI agents use to discover what a site can do: WebMCP tools in the page, and the MCP, A2A, agent skills, API catalog and OAuth documents under /.well-known.

Add up to 2 more pages (optional)

Paste a link or type a domain · No account · Private report

Want to choose which parts of the audit open your report? Use the full audit form.

What this checker tests

The scan runs the full CrawlWise audit. These checks answer this page's question; the report shows each one with its evidence.

What the checker reads

The scan records every tool the page registers through WebMCP, with its name, description and input schema, and fetches each discovery document from /.well-known:

Document Path
MCP server card /.well-known/mcp/server-card.json
A2A agent card /.well-known/agent-card.json
Agent skills index /.well-known/agent-skills/index.json
API catalog /.well-known/api-catalog
OAuth / OpenID discovery /.well-known/oauth-authorization-server, /.well-known/openid-configuration
OAuth protected resource /.well-known/oauth-protected-resource
ARD manifest /.well-known/ard.json

These protocols are new and several are drafts, so the checks are experimental with weight 0: they appear in their own report tab and never change the score.

Start with the basics

Agents still have to reach and read your pages first. Run the AI crawler checker and the JavaScript test before adding protocols, and read the agent-ready checklist to see which of them your kind of site needs. The WebMCP guide shows how to declare a tool.

FAQ

Does my website need an MCP server or WebMCP?

Only if agents should take actions on it or use its API. A content or marketing site is agent-ready without them. CrawlWise reports a missing document as not applicable and never lowers the score for it.

What is WebMCP?

A proposed browser API that lets a page register tools, such as search or booking, that a browser agent can call with structured input instead of clicking through the interface. Chrome offers it in an origin trial.

Where should an MCP server card live?

The draft puts it at /.well-known/mcp/server-card.json, with at least serverInfo.name. An A2A agent card lives at /.well-known/agent-card.json.

Why does my single-page app fail these checks?

Many single-page apps answer every path with their HTML shell and status 200. An HTML page at a /.well-known path is not a discovery document, so CrawlWise reports it as missing.

Related guides

More free checkers

Run the free check

Last updated .