Check an MCP server the way an agent does
This runs the opening handshake, reads the advertised tool list, and then tries to complete the loop that list implies. It is the same runner as pnpm dogfood:mcp, pointed at whatever endpoint you name.
Why this page exists
Two defects reached Ava’s own production server while 559 unit tests passed. The default tool list advertised the tools that approve and preview a plan, both of which need an executionId, while hiding the only tool that mints one. An agent discovering the server could see how to approve a plan and had no exposed call that creates one. Separately, a caller who named no chain landed on one with no live route, and was handed simulated balances that read like a position.
Neither is visible from inside a test suite, because both are properties of the surface an outside caller sees rather than of any function. Both were found by a person driving the server by hand. This page is that person, automated, and pointed at anyone’s server including ours.
Nothing here moves money. The run stops before the one call that settles, so the worst it can do to a server you point it at is create a session and ask for a plan.