MCP Compliance runs on your own machine — the client starts it, so there is no endpoint to ping. 250 installs a week from npm.
CLI tool and MCP server that tests MCP servers for spec compliance
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add mcp-compliance -- npx -y @yawlabs/mcp-compliance
{
"mcpServers": {
"mcp-compliance": {
"args": [
"-y",
"@yawlabs/mcp-compliance"
],
"command": "npx"
}
}
}
[mcp_servers.mcp-compliance]
command = "npx"
args = ["-y", "@yawlabs/mcp-compliance"]
{
"mcpServers": {
"mcp-compliance": {
"args": [
"-y",
"@yawlabs/mcp-compliance"
],
"command": "npx"
}
}
}
{
"mcpServers": {
"mcp-compliance": {
"args": [
"-y",
"@yawlabs/mcp-compliance"
],
"command": "npx"
}
}
}
Answers built from our own checks of this server.