mcp-protocol-conformance
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@mcp-protocol-conformancerun full conformance suite for my MCP server"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Part of the StudioMeyer MCP Stack โ Built in Mallorca ๐ด ยท โญ if you use it
mcp-protocol-conformance
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).
A note from us
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.
Related MCP server: MCP Test Server
Install
npm install --save-dev mcp-protocol-conformanceThe package ships both a CLI (mcp-conformance) and a TypeScript library entry (import ... from "mcp-protocol-conformance").
CLI usage
Run against a stdio server
mcp-conformance run \
--target stdio \
--cmd node \
--cmd-arg dist/server.js \
--spec 2025-06-18 \
--suite all \
--format terminalRun against an HTTP server (Streamable HTTP, 2025-03-26+)
mcp-conformance run \
--target http \
--url https://memory.studiomeyer.io/mcp \
--header "Authorization:Bearer ${TOKEN}" \
--spec 2025-06-18 \
--suite full \
--format json --out report.jsonRun only a subset of suites
mcp-conformance run --target stdio --cmd ./server --spec 2025-06-18 \
--suite jsonrpc,version,schemaCompare two manifests
mcp-conformance compare \
--expected manifests/v1.json \
--actual manifests/v2.jsonAssert no breaking changes between two reports
mcp-conformance assert-no-breaking \
--baseline reports/main.json \
--current reports/pr-42.jsonExit codes: 0 clean, 1 failures, 2 invocation error.
Library usage
import {
runFullSuite,
generateReport,
} from "mcp-protocol-conformance";
const report = await runFullSuite(
{ kind: "stdio", cmd: "node", args: ["dist/server.js"] },
"2025-06-18",
{ suite: "all" },
);
console.log(generateReport(report, "terminal"));
if (report.status === "fail") process.exit(1);MCP server usage
The harness is itself an MCP server. Start it over stdio and any MCP client can call its 12 tools:
node dist/server.jsTools (all read-only, all destructiveHint: false):
# | Tool | Purpose |
1 |
| JSON-RPC 2.0 error-code matrix + response-envelope (result/error mutual exclusivity) |
2 |
| Verify advertised protocolVersion |
3 |
| Transport-layer ping + session-id |
4 |
| OAuth 2.1 PKCE S256 (mock-AS or real-tenant) |
5 |
| inputSchema (+ 2025-11-25 outputSchema / title) is valid JSON-Schema |
6 |
| initialize.capabilities matches behaviour (+ 2025-11-25 tasks) |
7 |
| One tools/call per advertised tool |
8 |
| readOnlyHint / destructiveHint hygiene |
9 |
| All suites + summary |
10 |
| Render JUnit / JSON / terminal |
11 |
| Diff two tool manifests |
12 |
| Diff two FullReports |
Compatibility matrix
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.
Integration in Factory builds
In every Factory build's package.json:
{
"scripts": {
"factory:conformance": "mcp-conformance run --target stdio --cmd 'node dist/server.js' --spec 2025-06-18 --suite full"
}
}In CI:
- run: npm run factory:conformanceSpec references
JSON-RPC 2.0: https://www.jsonrpc.org/specification
MCP 2024-11-05: https://modelcontextprotocol.io/specification/2024-11-05
MCP 2025-03-26: https://modelcontextprotocol.io/specification/2025-03-26
MCP 2025-06-18: https://modelcontextprotocol.io/specification/2025-06-18
MCP 2025-11-25: https://modelcontextprotocol.io/specification/2025-11-25
RFC 7636 (PKCE): https://datatracker.ietf.org/doc/html/rfc7636
About StudioMeyer
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.
License
MIT โ Copyright (c) 2026 Matthias Meyer (StudioMeyer)
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/studiomeyer-io/mcp-protocol-conformance'
If you have feedback or need assistance with the MCP directory API, please join our Discord server