MCP signal detected but no /.well-known/mcp.json discovery manifest visible
This check looks for a /.well-known/mcp.json file, a small discovery file that tells AI tools like Claude Desktop, ChatGPT, Cursor and Continue how to connect to your MCP (Model Context Protocol) server. MCP signals were detected on this site, but no such manifest file was found. Recent MCP specification updates (SEPs 1649/1960, late 2025) make this file the canonical way AI tools discover an MCP server, and those tools all auto-detect from it. Without the manifest, your MCP server is effectively invisible to the agents it was built to be used by, regardless of how good the server itself is. Your engineering team should publish /.well-known/mcp.json describing your server's name, version, transport method, capabilities and authentication, and add a <link rel='mcp'> tag to your page's <head>. The specification is documented at modelcontextprotocol.io. Budget about a day for a developer to write and test it.
Why this matters
Recent MCP specification updates (SEPs 1649/1960, late 2025) make this file the canonical way AI tools discover an MCP server, and those tools all auto-detect from it. Without the manifest, your MCP server is effectively invisible to the agents it was built to be used by, regardless of how good the server itself is.
How to fix it
Your engineering team should publish /.well-known/mcp.json describing your server's name, version, transport method, capabilities and authentication, and add a <link rel='mcp'> tag to your page's <head>. The specification is documented at modelcontextprotocol.io. Budget about a day for a developer to write and test it.