An MCP probe that times out is treated as a fallback rather than a failed connection.
What's wrong with this entry?
MCP connect success and failure events now record which negotiation mode was used and whether the connection had to fall back after probing. In automatic negotiation mode, a request timeout during the Anthropic-side probe is now treated as a fallback case instead of a hard connection failure.
_anthropicProbeTimedOut
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.