Catch stdout pollution and handshake failures in MCP stdio servers before clients do.
Copy the install, test the workflow, then decide if it earns a permanent slot.
Still active enough to matter. Good candidate for a fast stack test instead of a long evaluation loop.
Copy the install, test the workflow, then decide if it earns a permanent slot.
You can test this quickly and remove it cleanly if it misses.
GitHub health unknown. no security policy. 1 open issues make this testable, but not something to trust blind.
AI Agent
Universal
Model
Multiple
Fastest way to find out if mcp-stdio-guard belongs in your setup.
Copy the install command, run a real test, and back it out cleanly if it slows you down.
git clone https://github.com/1Utkarsh1/mcp-stdio-guard ~/.claude/commands/mcp-stdio-guardRun this first. You will know quickly if the workflow earns a permanent slot.
rm -rf ~/.claude/commands/mcp-stdio-guardNo messy cleanup loop. If it misses, remove it and keep moving.
Install Location
~/ └─ .claude/ ├─ commands/ │ └─ mcp-stdio-guard/ ← installs here ├─ agents/ └─ settings.json
Catch stdout pollution and handshake failures in MCP stdio servers before clients do.