server/discover is implemented

How to fix this

Implement the `server/discover` method. It replaced the `initialize` handshake and is the first request a modern client makes, so a server that cannot answer it leaves most other rules unassessable.

How the validator checks this

Probe P1.1, against a streamable-http server on the modern protocol. What it reports:

pass

server/discover responded successfully

fail

server/discover did not return a usable response (…)

skip

server/discover requires authorization (HTTP 401), so conformance could not be assessed without a token. The authorization checks below still apply.

Quoted from the probe that runs this check, so it cannot drift from what the validator actually reports.

This rule is checked deterministically: a fail here is a certain violation, not an inference.

Checked in the same request as MCP-DSC-002, MCP-DSC-003, MCP-DSC-004, MCP-DSC-005, MCP-STL-003, MCP-RES-001, MCP-RES-002, MCP-RES-005.

Check your own server against this rule

The validator makes real protocol requests and reports this rule as pass, warn or fail alongside the other 78. Validate a server or read how the check works.

Other Discovery and capabilities rules

• MCP-DSC-002DiscoverResult advertises supported protocol versions
• MCP-DSC-003Advertised versions include a currently-supported revision
• MCP-DSC-004Extension identifiers use a valid non-reserved reverse-DNS prefix
• MCP-DSC-005Results carry io.modelcontextprotocol/serverInfo in _meta