MCP Protocol Conformance

Name: MCP Protocol Conformance
Author: studiomeyer-io

by studiomeyer-ioversion 0.2.2i★ –iRuns on your computer

Registry nameio.studiomeyer/protocol-conformance

Install

Overview

Description from the maker (original English)

MCP conformance test harness. JSON-RPC, OAuth 2.1 PKCE, schemas, smoke, annotations. CLI + lib.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Other

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
The registry lists no key to fill in.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "protocol-conformance": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-protocol-conformance"
      ]
    }
  }
}

Run this in your terminal

claude mcp add protocol-conformance -- npx -y mcp-protocol-conformance

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "protocol-conformance": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-protocol-conformance"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "protocol-conformance": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "mcp-protocol-conformance"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

✓ Pass
Maker matches the repo
The registry name was verified against the domain studiomeyer.io (the registry checks domain ownership)
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

More stars than 0% of the other 32461 servers in this category
Published to the registry more recently than 87% of the other 32461 servers in this category
Basic checks equal to or better than 100% of the other 32461 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is MCP Protocol Conformance safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.2.2) reached the registry 5 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, dotnet-mcp

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated yesterday

Install

dotnet-mcp

by Skymly

MCP server for .NET symbols, XAML, source generators, and restricted workspace edit

Runs on your computerUpdated today

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Part of the [StudioMeyer MCP Stack](https://studiomeyer.io) — Built in Mallorca 🌴 · ⭐ if you use it

mcp-protocol-conformance

Conformance test harness for Model Context Protocol servers. Validates JSON-RPC 2.0 wire compliance, spec-version handshake, transport behaviour, OAuth 2.1 PKCE, tool schemas, capability advertisement, smoke roundtrip, and annotation hygiene against MCP spec 2024-11-05, 2025-03-26, 2025-06-18, and the current stable revision 2025-11-25 (experimental tasks, structured tool output, JSON Schema 2020-12 default, tool title/icons).

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.

Install

npm install --save-dev mcp-protocol-conformance

The 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 terminal

Run 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.json

Run only a subset of suites

mcp-conformance run --target stdio --cmd ./server --spec 2025-06-18 \

--suite jsonrpc,version,schema

Compare two manifests

mcp-conformance compare \

--expected manifests/v1.json \ --actual manifests/v2.json

Assert no breaking changes between two reports

mcp-conformance assert-no-breaking \

--baseline reports/main.json \ --current reports/pr-42.json

Exit 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.js

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

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:conformance

Spec 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.

MCP Protocol Conformance

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

dotnet-mcp

README from the maker

mcp-protocol-conformance

A note from us

Install

CLI usage

Run against a stdio server

Run against an HTTP server (Streamable HTTP, 2025-03-26+)

Run only a subset of suites

Compare two manifests

Assert no breaking changes between two reports

Library usage

MCP server usage

Compatibility matrix

Integration in Factory builds

Spec references

About StudioMeyer

License