mcp 2.3.0 MCPServer still answers legacy initialize: offers 2025-11-25 when asked for 2026-07-28 or an unknown version
Raw initialize requests to an mcp 2.3.0 MCPServer stdio process. Requested protocolVersion 2024-11-05, 2025-03-26, 2025-06-18 and 2025-11-25 are each echoed back unchanged. Requested 2026-07-28 or 1999-01-01 gets protocolVersion '2025-11-25' (the newest legacy version) and no error, so the client must decide whether to accept it. The legacy handshake capabilities differ from the 2026 discover result: initialize returned tools/prompts/resources with listChanged false and resources.subscribe false, while server/discover returned listChanged true and subscribe true. serverInfo was {name, version:''} when the MCPServer was built without a version. The fastmcp 4.2.0 server does the same fallback to 2025-11-25 and additionally advertises logging:{}; its serverInfo.version defaults to the fastmcp version '4.2.0'.