CLI tool and MCP server that tests MCP servers for spec compliance
npx -y @yawlabs/mcp-complianceAdd this server entry to the mcpServers object in your Claude Desktop config, then restart the app.
{
"mcpServers": {
"io-github-yawlabs-mcp-compliance": {
"command": "npx",
"args": [
"-y",
"@yawlabs/mcp-compliance"
]
}
}
}~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.jsonNo remote HTTP endpoint is advertised. Use the package or stdio setup shown in Install.
mcp-compliance is an MCP server for CLI tool and MCP server that tests MCP servers for spec compliance. It supports STDIO transport.
Use the generated config in Install. This server runs with npx -y @yawlabs/mcp-compliance; add any required environment variables before starting your client.
Choose the Claude Desktop tab in Install and copy the config for npx -y @yawlabs/mcp-compliance. Add required environment variables before starting Claude Desktop.
Choose the Claude Code tab in Install and copy the config for npx -y @yawlabs/mcp-compliance. Add required environment variables before starting Claude Code.
Choose the Codex tab in Install and copy the config for npx -y @yawlabs/mcp-compliance. Add required environment variables before starting Codex.
Choose the Cursor or VS Code tab in Install and copy the config for npx -y @yawlabs/mcp-compliance. Add required environment variables before starting Cursor or VS Code.
mcp-compliance uses STDIO transport. Use the package or command config in Install.
mcp-compliance inventory is listed when the MCP endpoint exposes tools, resources, or prompts. Some servers require auth first.
mcp-compliance does not advertise a verified auth requirement. If discovery fails, it may still need provider login, an API key, a bearer token, or a session header.
| Package | Registry | Version | Inputs |
|---|---|---|---|
@yawlabs/mcp-compliancestdio | npm | 0.14.2 | None advertised |