Unverified50% confidenceFactExact time
In MCP's stdio mode, stdout is the protocol channel itself, and any non-protocol content mixed in causes the peer to fail parsing, so DSupport's server redirects System.out to System.err.
1
Sources
50%
Confidence
Long-term
Relevance
10/18/2026
First Seen
Sources
Related Entities
Related Claims
VerifiedMCP has a built-in Stdio (standard input/output) local communication mechanism, but Stdio cannot transmit across networks and can only be used for inter-process communication on a local machine.75% similarVerifiedIn stdio transport, MCP server logs must be written to standard error (stderr), because extraneous standard output will corrupt the protocol stream.75% similarUnverifiedv0.0.92 enables the Stdio MCP client to correctly handle EPIPE errors, preventing uncaught exceptions from being thrown when the server exits prematurely.74% similarUnverifiedThe three integration methods for MCP are STDIO (standard input/output streams), SSE (Server-Sent Events), and Streamable HTTP.71% similarVerifiedIn stdio mode, Claude Code launches the MCP Server as a child process, sending requests via stdin and receiving responses via stdout.71% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1062641API
curl https://kongchang.com/api/v1/knowledge/claims/1062641MCP
get_claim(id=1062641)