Vibeleaderboard
← All Intel
Intel / post

You can now skip the handshake and still call a tool and your retry after a time

Source
x.com
Date
AlphaSignal@AlphaSignalAI

You can now skip the handshake and still call a tool and your retry after a timeout can place two requests. We ran the retry on one laptop. The tool slept 2.5 seconds on purpose. > Wait 2.5 seconds > Abort around 400 ms > Log already at 1 > New id, second write Same sku. Same machine. A new request id is now a new call. Google said the old pin returned 400 Session Not Found on the wrong pod. GitHub already dropped Redis session reads and writes. Claude-only apps can often wait. Server authors cannot treat a hang-up as a rollback. What keeps a retry at one write? Where does a cart live with no session id? Do you still advertise the old revision?

Context

When a client hangs up on a tool call, the tool's action may already have happened, and a retry can do it a second time. AlphaSignal showed this on one laptop using the latest revision of the (MCP), the standard AI applications use to call outside tools. That July 28, 2026 revision retired the opening handshake and the session ID, so each request carries its own protocol version and client details and can be answered by any server instance. In AlphaSignal's test, an order-placing tool was made to wait 2.5 seconds; the client aborted at about 400 milliseconds, but the order log already showed one write. Retrying under a new request ID produced a second write, because, as the post puts it, a new request ID is now a new call.

The fuller write-up shows what kept the count at one: passing the same tool an order identifier (ord-42) let it answer that nothing was written because the order ID was a duplicate. The duplicate check therefore belongs to the application, keyed to the order itself, not to the request. MCP's maintainers make a related point in the revision's announcement: dropping the protocol session does not force an application to be stateless, and a server that needs state across calls should have a tool issue an explicit handle that the model passes back. AlphaSignal's conclusion is that apps used only through Claude or Cursor can often wait for their host to adopt the revision, while server and custom-client authors should treat a dropped answer as a full retry and make tools that write or charge safe to run twice.

Terms in this piece · Glossary
  • MCP — The Model Context Protocol — an open standard that lets any AI assistant plug into any tool or data source without custom integration code.
More from AlphaSignal
Recommended reads
Comments

Checking sign-in…

Loading comments…