You'll notice
Useful4 Signal2
MCP servers that flood the connection are cut off instead of endlessly eating memory.
What's wrong with this entry?
Anonymous. No account, no email.
What
Two new errors cut off a misbehaving MCP server: one for an oversized HTTP response body, one for a server that writes logs to stdout instead of stderr and so never produces a message boundary. Before this, that output accumulated without limit.
Details
- The stdio transport records the overflow error and closes the connection on the next tick rather than mid-read.
- The stdout error message names the likely cause directly, so the fix is to move server logging to stderr.
Evidence
without a JSON-RPC message boundary. The server is likely writing logs or other non-protocol data to stdout instead of stderr.
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.