Mcp Compliance
Verify MCP servers against the official spec using a CLI or MCP-exposed compliance runner before you ship or adopt them.
Overview
mcp-compliance is a MCP server for the Ship phase that tests MCP servers for Model Context Protocol specification compliance via CLI or MCP tools.
What is this MCP server?
- Dual mode: CLI tool and MCP server for MCP specification compliance tests
- npm package @yawlabs/mcp-compliance v0.15.1 with stdio transport
- Supports builders authoring custom MCP servers and vetting third-party servers
- Fits pre-ship checklists alongside security and code review habits
- Reduces silent spec mismatches that break agent hosts after upgrades
- Server version 0.15.1
- stdio transport per MCP server schema 2025-12-11
What problem does it solve?
Broken or partial MCP implementations waste hours when agents error only after you trusted a new server in production workflows.
Who is it for?
Indie developers building custom MCP servers or curating third-party MCP for their own catalog and team.
Skip if: Non-technical founders who only consume pre-vetted hosted tools and never author or audit MCP servers.
What do I get? / Deliverables
You get repeatable spec compliance results before shipping or installing MCP servers in your agent stack.
- Compliance test results for MCP servers
- CLI-runnable validation for CI pipelines
- MCP-invokable compliance checks from agents
Recommended MCP Servers
Journey fit
How it compares
MCP spec compliance tester, not a penetration test or application security audit skill.
Common Questions / FAQ
Who is mcp-compliance for?
Developers authoring MCP servers or responsible for which MCP packages their agent may use.
When should I use mcp-compliance?
Use it before releasing a server, after spec upgrades, or when evaluating an unfamiliar MCP package from the ecosystem.
How do I add mcp-compliance to my agent?
Install @yawlabs/mcp-compliance from npm, run the CLI in CI or register the stdio MCP server in your host for in-session tests.