Unverified50% confidenceFactExact time
Legacy MCP clients still use the initialize handshake to establish a session, and the server returns the legacy version (November 2025) and server information.
1
Sources
50%
Confidence
Medium-term (~90 days)
Relevance
10/28/2026
First Seen
Valid until: 1/26/2027
Sources
Building an MCP Server from Scratch: Let AI Apps Call Your Agent Tools
youtubeResearch Treats10/28/2026
Related Entities
Related Claims
VerifiedIn the 2026-07-28 revision, MCP removed the initialization handshake and protocol-level sessions, changing to a request-response model closer to stateless.79% similarUnverifiedMCP握手流程中Client发送initialize请求附带协议版本(如2024-11-05、2025-03-26)和可选能力列表,Server选择双方共同支持的最高版本回应78% similarUnverifiedAfter the MCP Host starts the MCP Server, a handshake is performed during which the Server reports its list of available Tools and their parameter information to the Host.76% similarUnverifiedIn the July 28, 2026 MCP specification revision, the initialize handshake and session ID were removed, each request carries its own version and capability information in the _meta field, server discover became optional; any request can land on any server instance, with just an ordinary load balancer in front.76% similarUnverifiedExisting MCP servers that rely on the initialize handshake or session headers need to adapt to the new _meta request structure and the server/discover call.76% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1108139API
curl https://kongchang.com/api/v1/knowledge/claims/1108139MCP
get_claim(id=1108139)