MCP server detail

Detail for a single MCP server.

Accepts both forms an agent might construct from a purl: • canonical id : 'owner/name' (what the DB stores) • purl form : 'mcp:owner/name' or 'pkg:mcp/owner/name'

Returns 200 in both the registered and the genuinely-unknown cases. The previous 404-on-unknown behaviour was the dominant source of 4xx noise on the admin dashboard — every LLM agent that hit this endpoint for a server we don't index would 404, and the agent had no actionable JSON to feed back to the user. Now the response is uniform-shape: missing servers come back with trust_tier='unverified' + source='not_in_registry' so the prompt's existing 'unknown → require explicit confirmation' branch handles them without special-casing.