![[Showcase] mcp-stdio-guard catches stdout pollution in MCP stdio servers](https://external-preview.redd.it/dkDtN80F05rbCm36345Hfn9_WxPsJLdLgy1PzOu0Kgc.png?width=1080&crop=smart&auto=webp&s=839529a36f096d7243fcf768da967bbc103b691e)
▲ 1 r/mcp
[Showcase] mcp-stdio-guard catches stdout pollution in MCP stdio servers
I built a small open-source CLI for MCP server authors who use stdio transport.
The problem it checks for is simple but painful: any console.log(), print(), or other stdout text can corrupt the JSON-RPC stream. The tool runs a real initialize handshake, optionally sends a request like tools/list, allows stderr logs, and fails on stdout pollution, invalid JSON-RPC frames, crashes, timeouts, or missing responses.
Install/test:
npx --yes mcp-stdio-guard -- <your-server-command>
Repo:
https://github.com/1Utkarsh1/mcp-stdio-guard
I would love feedback from people building MCP servers: what other stdio/protocol failures should it catch?
u/Dear_Lock_5280 — 1 day ago