MCP Server Testing Is Fragmented. I Built One CLI for Record, Replay, Mock, Audit, and CI

I've been building MCP servers for a bit, and the testing story has always bugged me. Not because there are zero tools — there are. The MCP Inspector lets you connect to a server and poke around. You can write scripts with the MCP SDK. You can unit test your server's internal logic. These all work fine for what they do. The problem is what happens after that. The actual problem You build an MCP server. You test it manually or with a few scripts. It works. You ship it. Then you change something — a tool's input schema, a response format, a dependency — and you have no idea what you just broke. There's no regression test. There's no way to replay what worked before and see what's different now. Your teammates want to build against your server, but they need API keys and a running instance. Your CI pipeline doesn't check whether the server actually works. And nobody's auditing whether the tool descriptions contain anything sketchy. Each of these problems has a solution in isolation. But t