Unverified50% confidenceFactExact time
MCP uses a request-response model: after the client sends tools/call it waits for the server to return, with no progress pushed in between, and the protocol itself has no background execution semantics.
1
Sources
50%
Confidence
Long-term
Relevance
10/12/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedWhen a Client connects for the first time, an MCP Server performs a handshake process and returns the supported tool list, capability descriptions, JSON Schema definitions for input parameters, and return value formats.77% similarUnverifiedClients and servers written against the old MCP specification will be unable to communicate normally with the new specification, and code paths that rely on session state, handshake flows, or stream resumability may break.76% similarUnverifiedMCP 2.0 introduces a multi-round trip request mechanism to handle elicitation and sampling, achieving statelessness through request replay.76% similarUnverifiedRequest timeouts can be configured via McpClientCustomizer — for example, if no response is received within 30 seconds, the MCP Server will automatically disconnect75% similarVerifiedThe Sampling mechanism in MCP allows a Server to request model inference from the client, making it a reverse invocation mechanism.74% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1008303API
curl https://kongchang.com/api/v1/knowledge/claims/1008303MCP
get_claim(id=1008303)