new·The score now tells you which way it movedA brain's exam only ever grows: its own material writes questions, and so does every question a real caller asked and did not get answered. The score is a percentage over that growing set, so a brain that learned more could post a smaller number — and this week three did. One of them answered two MORE questions than the week before and showed eighteen points less. Printed as a single percentage, that reads as decline to a reader and as punishment to anyone who contributes material.all news →
mozg.beta
Sign in

MCP · Building servers and clients · all subjects

transports: streamable http

4 notes, read out of this brain and free to use. Each one was extracted from a source and is re-checked against its exam.

MCP 2026-07-28 Streamable HTTP requires Mcp-Method and Mcp-Name headers

The Streamable HTTP transport in MCP 2026-07-28 requires Mcp-Method and Mcp-Name headers (SEP-2243) so load balancers, gateways, and rate-limiters can route on the operation without inspecting the body. Servers reject requests where the headers and body disagree.

Example 2025-11-25 Streamable HTTP request with session

In MCP 2025-11-25, calling a tool over Streamable HTTP requires first establishing a session with an initialize request: POST /mcp HTTP/1.1, Content-Type: application/json, body contains jsonrpc 2.0 with id, method initialize, protocolVersion 2025-11-25, empty capabilities, and clientInfo. The server responds with an Mcp-Session-Id header that every subsequent request must carry.

Example 2025-11-25 Streamable HTTP tool call with session

In MCP 2025-11-25, after receiving an Mcp-Session-Id from initialize, subsequent tool calls look like: POST /mcp HTTP/1.1, Mcp-Session-Id: [session-id], Content-Type: application/json, with jsonrpc 2.0 containing id, method tools/call, and params with tool name and arguments. The Mcp-Session-Id header pins the client to one instance.

Example 2026-07-28 Streamable HTTP self-contained request

In MCP 2026-07-28, a tool call is a single self-contained request: POST /mcp HTTP/1.1, MCP-Protocol-Version: 2026-07-28, Mcp-Method: tools/call, Mcp-Name: search, Content-Type: application/json, body contains jsonrpc 2.0 with id, method tools/call, params with tool name, arguments, and _meta containing io.modelcontextprotocol/clientInfo with name and version. Any server instance can handle this request.

Give your agent this brain