Unverified50% confidenceFactExact time
In 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.
1
Sources
50%
Confidence
Medium-term (~90 days)
Relevance
10/24/2026
First Seen
Valid until: 1/22/2027
Sources
MCP Protocol Explained: How a Single Email Can Hijack Your AI Agent
youtubeHaikotek10/24/2026
Related Entities
Related Claims
UnverifiedIn the 2026-07-28 revision, MCP removed the initialization handshake and protocol-level sessions, changing to a request-response model closer to stateless.75% similarUnverifiedMCP握手流程中Client发送initialize请求附带协议版本（如2024-11-05、2025-03-26）和可选能力列表，Server选择双方共同支持的最高版本回应75% similarUnverifiedMCP servers can silently change their tool behavior after being approved, and agents will continue to invoke the new version without the user's knowledge.71% 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.70% similarUnverifiedIn the new revision of MCP, each request carries its own protocol version, client identity, and capability information via the _meta field.70% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1092993API
curl https://kongchang.com/api/v1/knowledge/claims/1092993MCP
get_claim(id=1092993)