MCP endpoint absent

What it detects

No /.well-known/mcp.json or other Model Context Protocol discovery file is published.

Why it matters

MCP is the standard way for an agent to discover a site's callable tools (search, product lookup, checkout) instead of reverse-engineering them from the UI; without it, every agent integration has to be built by hand.

How to fix

- Check for a `/.well-known/mcp.json` discovery file or another Model Context Protocol (MCP) discovery endpoint. - Implement an MCP server exposing the site's key capabilities as tools (search products, get product details, check availability, add to cart, etc.) and publish `/.well-known/mcp.json` describing the endpoint, transport, and version. - Reuse existing internal APIs as the implementation behind each MCP tool rather than building new business logic — MCP is a discovery/interface layer, not a new backend. - Verify: `curl` `/.well-known/mcp.json`, confirm it returns valid JSON with `version`, `endpoint`, and `transport`, and exercise at least one tool call against the MCP endpoint (see modelcontextprotocol.io for SDKs and conformance guidance).

References

• MCP — server discovery
• WAI-ARIA 1.2 (W3C)