What core MCP functionality requires the server to initiate requests to the client?	Sampling, notifications, and logging.
What is the primary challenge when using standard HTTP to achieve server-initiated requests to a client?	Standard HTTP makes it difficult to allow the server to make a request to the client.
When using the HTTP transport, what unique identifier is included in the server's initial response header?	The MCP session ID.
What specific type of response is used as the workaround to allow the server to stream messages to the client?	Server-Sent Events (SSE) response.
What must the client include in all follow-up requests after initialization to allow the server to identify the connection?	The MCP session ID.
When a client calls a tool, how many separate SSE connections are typically established?	Two (one long-lived connection, and one temporary connection for the call).
Which type of message (progress notification or result) is sent via the long-lived SSE connection?	Progress notifications.
Which type of message (progress notification or result) is sent via the temporary SSE connection created for a tool call?	Logging messages and the final call tool result.
What happens to the temporary SSE connection used for a tool call?	It closes automatically as soon as the call tool result message is sent.
What is the consequence of setting certain transport flags to `true`?	It breaks the streamable HTTP workaround flow.