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

server implementation patterns

2 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 explicit-handle pattern for application state

Removing protocol-level sessions does not require applications to be stateless. Servers that need to carry state across calls can mint an explicit handle (a basket_id, browser_id) from a tool and have the model pass it back as an ordinary argument on later calls. This pattern makes state visible to the model rather than hidden in transport metadata, allowing the model to compose handles across tools and reason about them.

Handle pattern sequence diagram in MCP

The handle pattern for stateful applications in MCP: the model calls create_basket and the MCP server returns a basket_id; the model then passes that same basket_id back as an argument to add_item. This makes state visible to the model rather than hidden in transport metadata.

Give your agent this brain