Compliance MCP Server

Test any MCP server for spec compliance. 88-test suite covering transport, lifecycle, tools, resources, prompts, error handling, schema validation, and security against the MCP specification. Works against HTTP endpoints (https://my-server.com/mcp) and stdio servers (npx @modelcontextprotocol/server-filesystem /tmp) alike. CLI, MCP server, and programmatic API.

People who work with mcp and compliance and want it reachable from Claude, Cursor, VS Code, or another MCP client. The project is written in TypeScript.

VERIFIED ACTIVE

LAST COMMIT 2026-09-17 · ★ 2 · #147 OF 945 MAINTAINED OTHER · VERIFIED 2026-09-18

MIT · TypeScript servers · how we verify → /methodology

01 · Install Compliance

before you install - you'll need

LOG_LEVEL

Environment variables documented in the project's README - it lists which are required and which have defaults.

Claude Code

claude mcp add yawlabs-mcp-compliance -- npx -y @yawlabs/mcp-compliance

Claude Desktop / Cursor / VS Code - add to config

{
  "mcpServers": {
    "yawlabs-mcp-compliance": {
      "command": "npx",
      "args": [
        "-y",
        "@yawlabs/mcp-compliance"
      ]
    }
  }
}

Same JSON for Cursor. For VS Code, rename the top-level key from `mcpServers` to `servers`.

Using another client? Same JSON, different key

Claude Desktop · mcpServers

Cursor · mcpServers

VS Code · servers

Windsurf · mcpServers

Zed · context_servers

Cline · mcpServers

Roo Code · mcpServers

Continue · mcpServers

LibreChat · mcpServers

Gemini CLI · mcpServers

Codex CLI · mcp_servers

Full setup guides: every client.

02 · Evidence

Security posture

What to check before giving this server access to your agent - from the registry, GitHub, and our own probes. We don't score safety; we show what's verifiable.

runs as local process (stdio) - runs on your machine with your user's permissions

license MIT - declared in the repository

npm package @yawlabs/mcp-compliance - published under the repo owner's npm scope (@yawlabs)

registry namespace io.github.YawLabs is GitHub-verified and matches the repo owner

03 · What Compliance can do

Prose above is summarized from the project's README and registry record - no invented capabilities.

What you can build

An agent gets 2 documented tools spanning mcp, compliance, including mcp_compliance_test, mcp_compliance_explain.

The 2 tools it gives your agent

Extracted from the project's README - what MCP Compliance lets an agent do.

mcp_compliance_test: - 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
mcp_compliance_explain: - Explain what a specific test ID checks and why it matters.

Latest releases

v0.18.2 · 2026-09-15

Security · undici is now ^8.9.0 (was ^8.7.0) and @modelcontextprotocol/sdk is now ^1.30.0 (was ^1.29.0); npm audit goes from 10 findings (5 high) to 0. Both are runtime dependencies that tsup leaves external, and…

v0.18.1 · 2026-09-14

Changed · npm and MCP Registry listing metadata: bugs URL, core keywords, and server.json title/repository/websiteUrl · release.sh writes a ## [x.y.z] changelog entry for every release - promoting [Unreleased] when it…

v0.18.0 · 2026-09-14

No runtime changes; the published package behaves exactly as 0.17.4. · Changed · release.sh waits for npm to actually serve the new version before the MCP Registry step. npm publish returns as soon as the registry…

04 · Who maintains Compliance

MCP Compliance is maintained by yawlabs. We track 12 MCP servers from yawlabs - 12 actively maintained, 77 combined GitHub stars, oldest repo from Apr 2026. Full record: all servers from yawlabs.

05 · Facts

repository: github.com/yawlabs/mcp-compliance
website: https://yaw.sh/mcp-servers/mcp-compliance/
category: other - ranked #147 of 945 actively-maintained other servers as of 2026-09-18.
release cadence: 9 releases in the last 90 days (latest 2026-09-15)
registry: io.github.YawLabs/mcp-compliance (active, first published 2026-05-15 · 16 versions)
packages: npm:@yawlabs/mcp-compliance

06 · Compliance FAQ

What is Compliance?

Is Compliance still maintained?

Yes - as of 2026-09-18, its last commit was 2026-09-17 and it shipped 9 releases in the last 90 days. We re-verify nightly.

How do I install Compliance?

Run `npx -y @yawlabs/mcp-compliance`. The README documents one environment variable (LOG_LEVEL) to set first. You can also paste the ready-made client config above.

Does Compliance run locally?

Yes - it's a stdio server: it runs on your machine (via npx) with your user's permissions. Your data stays local unless the server itself calls external APIs.

07 · Alternatives to Compliance

Alternatives to Compliance

Maintained other servers if Compliance isn't the fit.

More MCP servers to compare · SSH MCP Server (yawlabs) · Tailscale MCP Server · 1c Platform Tools · Siren · Time MCP

More TypeScript MCP servers · npm Registry MCP Server · PostgreSQL MCP Server (yawlabs) · Redis MCP Server · see all