MCP server not launched
/mcp/ is presently a human-readable status page. It does not accept MCP JSON-RPC, advertise tools, or establish a Streamable HTTP session. A separate stdio consumer pack talks to a correspondence origin you already operate; that archive is not this path and is not a hosted MCP server.
§ FutureLaunch condition
A card or registry record follows a real server.
- Published tools must exist and return the stated schemas.
- Every operation must name its resource and authorization boundary.
- Opaque handles cannot substitute for resource-bound authorization.
- Credential, audit, expiry, and revocation paths must be testable.
- Human documentation will move away from the protocol path before launch.