Verified65% confidenceFactExact time
MCP clients and servers complete the handshake and mutually declare their capability sets via initialize / initialized messages.
3
Sources
65%
Confidence
Long-term
Relevance
7/21/2026
First Seen
Sources
Related Claims
UnverifiedExisting 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.80% similarVerifiedWhen 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.76% similarUnverifiedMCP Host在启动MCP Server后会进行握手，Server会向Host报告其可用的Tool列表及参数信息75% similarVerifiedAfter an MCP client connects to a server, it first performs Capability Negotiation to query the tools, resources, and prompt templates provided by the server71% similarVerifiedMCP's design philosophy is full registration — tool descriptions from all servers are injected into the context all at once during session initialization.71% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/580004API
curl https://kongchang.com/api/v1/knowledge/claims/580004MCP
get_claim(id=580004)