MCP gained popularity because it was as easy as building a REST API. Infact, many might say, building an MCP Server is a bit too easy. Shipping a broken MCP server into a pool of a hundred others is easy but shipping one that actually behaves correctly under adversarial clients, malformed inputs, and edge-case tool schemas is hard.
Devs have already built tens of thousands of MCP servers, and recent spec revisions have focused on richer tool annotations, structured tool outputs, and clearer security best practices, all of which introduce new failure modes to test for.
This session covers a complete testing pyramid for MCP servers: using the official MCP Inspector for interactive tracing, writing conformance tests against the JSON Schema tool definitions, and applying property-based testing (with tools likeHypothesis in Python or fast-check in TypeScript) to fuzz tool inputs and surface schema violations before clients do. We'll also walk through how to set up a CI pipeline that runs your MCP server against a spec conformance suite on every pull request, and how to lint tool descriptions for ambiguity that could confuse real LLM clients.
Navin is a Founding Engineer at OpsVerse. You'll often find him on the internet, getting into flamewars about observability, large scale system design, and open source software
