MCP endpoint absent
MCP_ENDPOINT_ABSENT · v2.0
Computed by Scovant Core ≥ 0.10.0 (open source) — pin that version and you get the same verdict.
What it detects
No Model Context Protocol surface is published: no valid /.well-known/mcp.json discovery file, no MCP server card at the well-known paths, and no server card listed in an AI Catalog at /.well-known/ai-catalog.json. A /.well-known/mcp.json that answers with an HTML page or other non-discovery JSON does not count.
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 — a `/.well-known/mcp.json` that answers with an HTML page or JSON without an `mcpServers` server does not count. - Or publish an AI Catalog at `/.well-known/ai-catalog.json` whose entry points at your MCP Server Card (SEP-2127, media type `application/mcp-server-card+json`). - 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
Last reviewed: 2026-09-01 · rule v2.0