You'll notice
Useful4 Signal3
An MCP probe timeout now retries on the older protocol instead of failing the connection.
What's wrong with this entry?
Anonymous. No account, no email.
What
When auto-negotiating an MCP server's protocol version, a discovery probe that times out is now detected and the connection retried against the pinned legacy protocol within the remaining time budget, instead of the connect failing outright.
Details
- If that legacy retry fails for an unrelated reason, the original timeout classification is kept so the connect stays eligible for the normal retry ladder.
- When the probe decides a server is legacy from an id mismatch, malformed response or early stream end, the reason is now recorded and written to the MCP debug log.
Evidence
era probe classified the server legacy in-SDK
Strings lifted out of the shipped bundle, so the claim above can be checked against them.