False: a reply to a server->client request travels on a *different* HTTP
request than the one whose inbound stream delivered it, and a nested
synchronous POST from inside an awaiting read loop could deadlock the
connection. McpClient therefore defers the reply to a background task
(which the HTTP transport already runs under an event loop).
False: a reply to a server->client request travels on a *different* HTTP request than the one whose inbound stream delivered it, and a nested synchronous POST from inside an awaiting read loop could deadlock the connection. McpClient therefore defers the reply to a background task (which the HTTP transport already runs under an event loop).