Unverified50% confidenceFactExact time
The older version of MCP (1.0) required remote servers to use persistent connections or sticky routing.
1
Sources
50%
Confidence
Long-term
Relevance
9/16/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedUnder the old MCP specification, GitHub MCP and many distributed MCP servers could not support elicitation, because it requires cross-server communication to coordinate state and sessions.76% similarVerifiedRemote MCP services adopt the Streamable HTTP mode, based on HTTP/1.1 or HTTP/2 protocols, with support for Server-Sent Events (SSE).76% similarUnverifiedThe stateful persistent connection mode of older MCP versions has a fundamental conflict with the ephemeral execution model of Serverless.75% similarUnverifiedSupporting the new MCP protocol itself is straightforward; what is truly tricky is the large amount of undefined behavior present in wild MCP servers.74% similarUnverifiedBrowser Tools MCP的浏览器扩展与MCP Server之间通过WebSocket建立持久连接74% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/925511API
curl https://kongchang.com/api/v1/knowledge/claims/925511MCP
get_claim(id=925511)