@Modelcontextprotocol/Server
An MCP server accessed over HTTP may deliver responses and notifications from one client to another. This occurs when clients share a single stateless transport, `McpServer` instance, or `Server` instance. The issue stems from messages being matched to a connection using only the JSON-RPC `id`. Since SDK clients typically start numbering requests from 0, these identifiers collide during normal operation.