MCP conformance test harness. JSON-RPC, OAuth 2.1 PKCE, schemas, smoke, annotations. CLI + lib.
Copy the AI prompt to install this server into Claude Code, Cursor, or another agent β or use 1-click editor setup below.
π‘ Paste the JSON block into your client's configuration file under mcpServers, then restart the application.
Part of the StudioMeyer MCP Stack β Built in Mallorca π΄ Β· β if you use it
This is a Foundation build of the StudioMeyer MCP Factory: every other Factory build runs through this harness before promotion (npm publish, marketplace submit, upstream PR).
We have been building tools and systems for ourselves for the past two years. The fact that this repo is small and has few stars is not because it is new. It is because we only just decided to share what we have built. It is not a fresh experiment, it is a long story with a recent commit.
We love building things and sharing them. We do not love social media tactics, growth hacks, or chasing stars and followers. So this repo is small. The code is real, it gets used, issues get answered. Judge for yourself.
If it helps you, sharing, testing, and feedback help us. If it could be better, an issue is more useful. If you build something with it, tell us at hello@studiomeyer.io. That genuinely makes our day.
From a small studio in Palma de Mallorca.
The package ships both a CLI (mcp-conformance) and a TypeScript library entry (import ... from "mcp-protocol-conformance").
Exit codes: 0 clean, 1 failures, 2 invocation error.
The harness is itself an MCP server. Start it over stdio and any MCP client can call its 12 tools:
Tools (all read-only, all destructiveHint: false):
| # | Tool | Purpose |
|---|---|---|
| 1 | runJsonRpcCompliance | JSON-RPC 2.0 error-code matrix + response-envelope (result/error mutual exclusivity) |
| 2 | runSpecVersionAssertion | Verify advertised protocolVersion |
| 3 | runTransportSuite | Transport-layer ping + session-id |
| 4 | runOauthPkceFlow | OAuth 2.1 PKCE S256 (mock-AS or real-tenant) |
| 5 | runToolSchemaValidation | inputSchema (+ 2025-11-25 outputSchema / title) is valid JSON-Schema |
| 6 | runCapabilityIntrospection | initialize.capabilities matches behaviour (+ 2025-11-25 tasks) |
| 7 | runRoundtripSmoke | One tools/call per advertised tool |
| 8 | runAnnotationsAudit | readOnlyHint / destructiveHint hygiene |
| 9 | runFullSuite | All suites + summary |
| 10 | generateReport | Render JUnit / JSON / terminal |
| 11 | compareManifests | Diff two tool manifests |
| 12 | assertNoBreakingChanges | Diff two FullReports |
| 2024-11-05 | 2025-03-26 | 2025-06-18 | 2025-11-25 | |
|---|---|---|---|---|
| jsonrpc | yes | yes | yes | yes |
| version (handshake) | yes | yes | yes | yes |
| transport (stdio) | yes | yes | yes | yes |
| transport (http) | n/a | yes | yes | yes |
| oauth (mock) | n/a | yes | yes | yes |
| oauth (real) | n/a | yes | yes | yes |
| schema | yes | yes | yes | yes |
| capability | yes | yes | yes | yes |
| smoke | yes | yes | yes | yes |
| annotations | warn-only | warn-only | yes | yes |
| tasks (capability) | n/a | n/a | n/a | yes |
| tool title/output | n/a | n/a | n/a | warn-only |
yes = suite runs and produces actionable results.
n/a = capability not in spec; suite skips automatically.
warn-only = suite runs but the spec does not formally require the feature.
The 2026-07-28 RC (stateless core, SEP-2575/2567) is intentionally not here β it ships final on 2026-07-28; conformance for it lands in a later release against the final SDK.
In every Factory build's package.json:
In CI:
StudioMeyer is an AI and design studio based in Palma de Mallorca, working with clients worldwide. We build custom websites and AI infrastructure for small and medium businesses. Production stack on Claude Agent SDK, MCP and n8n, with Sentry, Langfuse and LangGraph for observability and an in-house guard layer.
MIT β Copyright (c) 2026 Matthias Meyer (StudioMeyer)
No reviews yet β be the first to share how this listing worked for you.
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
[](https://allmcps.com/mcp/mcp-protocol-conformance)<a href="https://allmcps.com/mcp/mcp-protocol-conformance"><img src="https://allmcps.com/api/badge/mcp-protocol-conformance?style=directory" alt="MCP Protocol Conformance on AllMCPs" /></a>