MCP Compliance

yawlabs/mcp-compliance

You'd reach for this when building or maintaining an MCP server and need to verify it actually follows the spec correctly. It works as both a standalone CLI tool for testing during development and as an MCP server itself, which is a neat meta approach. Run it against your server implementation to catch compliance issues before they become integration problems. Especially useful if you're publishing a server publicly or need to validate that spec changes haven't broken your implementation. The dual mode means you can automate checks in CI or test interactively.

GitHub stars: 2
tools: 2
transport: STDIO
last updated: Nov 12, 2026

View on GitHub

Tools

2 tools

Public tool metadata for what this MCP can expose to an agent.

mcp_compliance_testRun the full compliance suite against an HTTP MCP endpoint (URL). Supports auth, custom headers, timeout, retries, category/test filtering, and specVersion (auto | 2025-11-25 | 2026-07-28, default auto). Returns grade, score, the resolved specVersion, and detailed results (eac...

Run the full compliance suite against an HTTP MCP endpoint (URL). Supports auth, custom headers, timeout, retries, category/test filtering, and specVersion (auto | 2025-11-25 | 2026-07-28, default auto). Returns grade, score, the resolved specVersion, and detailed results (eac...

No parameter schema in public metadata yet.

mcp_compliance_explainExplain what a specific test ID checks and why it matters, with a link to the spec section. Ids are per catalog: pass specVersion to read one catalog, or omit it to search both.

Explain what a specific test ID checks and why it matters, with a link to the spec section. Ids are per catalog: pass specVersion to read one catalog, or omit it to search both.

No parameter schema in public metadata yet.