MCP and API Discovery Checker
If a site exposes APIs or tools, agents need machine-readable discovery before they can understand capabilities, auth, limits, and safe entry points.
- Surface
- Free tool
- Scope
- Public web evidence
- Auth
- None required
- Schema
- SoftwareApplication
Answer first
What it checks
The scan fetches API catalogs, OpenAPI candidates, OAuth/OIDC metadata, protected-resource metadata, MCP server cards, A2A cards, and agent skill indexes.
Detail 01
Applicability matters
Not every website needs MCP or OAuth metadata. Missing advanced protocol files are treated as actionable only when matching public surfaces are detected.
Detail 02
What to publish
Expose stable .well-known metadata, keep OpenAPI current, document auth truthfully, and avoid claiming MCP support unless real transport exists.
FAQ
Common questions
- Do I need MCP for a normal marketing site?
- Usually no. MCP metadata is useful when you expose agent-callable tools or server capabilities, not when the site only publishes static pages.
- Does isitready.dev implement an MCP server?
- No public MCP transport is claimed here. This checker validates discovery metadata and public scan evidence.