Capability-driven
tests adapt to what the server declares. If it says it supports tools, tool tests become required. No false failures for features the server doesn't claim.
How to use it
Project documentation lists Capability-driven for the MCP Compliance MCP server. Add the server to your MCP client (Claude Desktop, Cursor, Windsurf and others), then check which tools your installed version makes available. Tool availability can depend on configuration and credentials. A server handshake does not verify this tool’s behavior. See the full listing for setup details.
Install MCP Compliance
npx @yawlabs/mcp-compliance@latest test https://my-server.com/mcpOther tools in MCP Compliance (4)
--strict mode exits with code 1 on required test failures. Drop it into any pipeline.
Explain what a specific test ID checks and why it matters.
Run the full 88-test suite against a URL or stdio command. Supports auth, custom headers, env vars, timeout, retries, and category/test filtering. Returns grade, score, and detailed results.
every test links to the exact section of the MCP specification it validates. No ambiguity about what's being tested or why.