Ten MCP servers I shipped this year. I use three.

I shipped ten Model Context Protocol servers under one npm scope this year. Three I use multiple times a week. Seven sit in my config file as dead weight. This is the honest ranking. The pattern is uncomfortable for the MCP-everywhere hype cycle, so I want to write it down.

The three I actually use

streamparse-mcp parses partial / truncated JSON. The trigger is the same every time: Claude is streaming output that should be JSON, the stream cuts off, I need to recover what was emitted. Asking the MCP is faster than remembering the JSON.parse recovery dance.

mcpcheck lints MCP config files. Errors in MCP configs are silent. Nothing crashes. The tool just is not there. A two-second lint catches the typo before ten minutes of "why does Claude not see my server."

agentvet-mcp validates tool-call args before execution. Lets Claude pilot a tool I have not fully trust-listed. The LLM-friendly hints make Claude self-correct better than a stack trace would.