@@ -146,7 +146,7 @@ The Model Context Protocol separates the AI application that needs a capability
 
 ## How an MCP server works
 
-An MCP server exposes selected capabilities to an AI application through structured requests. Under the October 2026 specification, each request declares its protocol version and client capabilities in metadata; the server accepts or rejects that request independently. This replaced the initialization handshake used by protocol revisions through 2025. The client can list the tools, resources, or prompts available from the server. Client and server exchange JSON-RPC messages through a supported transport, such as standard input and output for local processes or Streamable HTTP for remote communication. The [July 2026 MCP changelog](https://modelcontextprotocol.io/specification/2026-07-28/changelog) documents the stateless request model and removal of protocol-level sessions.
+An MCP server exposes selected capabilities to an AI application through structured requests. The October 2026 specification distinguishes two connection flows: the `2026-07-28` revision and later use a stateless model in which every request declares its protocol version and client capabilities in metadata, while revisions through `2025-11-25` negotiate the version and capabilities with an `initialize` handshake. Sim currently supports the handshake-based flow: its MCP client initializes connections, and its workflow MCP server handles `initialize` and negotiates an SDK-supported protocol version. The client can then list the tools, resources, or prompts available from the server. Client and server exchange JSON-RPC messages through a supported transport, such as standard input and output for local processes or Streamable HTTP for remote communication. The [July 2026 MCP changelog](https://modelcontextprotocol.io/specification/2026-07-28/changelog) documents the newer stateless request model and removal of protocol-level sessions, while the [MCP versioning specification](https://modelcontextprotocol.io/specification/2026-07-28/basic/versioning) defines modern, legacy, and dual-era compatibility.
 
 The [official MCP specification](https://modelcontextprotocol.io/specification/latest) groups server capabilities into tools, resources, and prompts. Each capability has a different purpose and uses its own discovery and request methods. A server can expose any subset of these capabilities.
 
@@ -186,7 +186,7 @@ An MCP client is the protocol component inside a host that establishes and maint
 
 ### What is the difference between an MCP host and an MCP client?
 
-The host manages the model, user experience, consent, security policy, and capability selection. Each client handles initialization, discovery, requests, responses, and notifications for its server connection. The [official MCP client documentation](https://modelcontextprotocol.io/docs/2025-11-25/learn/client-concepts) confirms that a host can coordinate multiple clients while each client communicates directly with one server.
+The host manages the model, user experience, consent, security policy, and capability selection. For the handshake-based revisions that Sim currently supports, each client handles initialization, discovery, requests, responses, and notifications for its server connection. The [official MCP client documentation for the `2025-11-25` revision](https://modelcontextprotocol.io/docs/2025-11-25/learn/client-concepts) confirms that a host can coordinate multiple clients while each client communicates directly with one server.
 
 ### Which transports do MCP servers use?