MCP.Market

MCP Protocol Conformance MCP server

by studiomeyer.io·io.studiomeyer/protocol-conformance·v0.2.2

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

A86/100grade A
What users say
No reviews yet
Be the first
Safety scan
A86/100

full report

Adoption
Growing

0 stars305 downloads/wk

Reviews

Write one

Nobody has reviewed MCP Protocol Conformance yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

MCP Protocol Conformance tools (5, 5 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • runJsonRpcCompliancewrite action

    Run JSON-RPC 2.0 compliance suite (parse-error, invalid-request, method-not-found, invalid-params, internal-error) against a target MCP server.

  • runOauthPkceFlowwrite action

    Exercise OAuth 2.1 PKCE S256 flow against the target. Mock-AS by default; real-tenant when --oauth-mode=real.

  • runSpecVersionAssertionwrite action

    Drive an initialize handshake and assert the target advertises the expected MCP spec version.

  • runToolSchemaValidationwrite action

    Validate that every advertised tool has a well-formed JSON-Schema inputSchema. Optionally diff against an expected manifest.

  • runTransportSuitewrite action

    Verify the target's transport layer (stdio line-delimited JSON or Streamable HTTP).

Public scan report

scanner v0.1.10 · 2026-11-02 · same rubric, same numbers if you re-run it

no findings
  • Code scan57 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 1 days ago15/15
  • Maintainer identitynamespace and repository owner differ4/10
Overall 86/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How MCP Protocol Conformance compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
86/100
higher than 72% of 48,243 servers
Tools
5
the typical server has 7
Tools that change things
100%
typical: 0%. Fewer write tools means less an agent can break
Downloads a week
305
more than 81% of 12,306 servers with a package

What its tools let an agent do: 5 run or deploy

Release history: 2 versions in the registry since 2026-08-19, latest 2026-11-01, typically one every 74 days.

Install MCP Protocol Conformance in Claude Code, Cursor or VS Code

Runs npx -y mcp-protocol-conformance on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add protocol-conformance -- npx -y mcp-protocol-conformance
Add to Cursor

What the publisher says

From the MCP Protocol Conformance repository's README, as published. We do not edit it. Read it on GitHub

<!-- studiomeyer-mcp-stack-banner:start -->

Part of the StudioMeyer MCP Stack — Built in Mallorca 🌴 · ⭐ if you use it

<!-- studiomeyer-mcp-stack-banner:end -->

mcp-protocol-conformance

<!-- badges --> <!-- /badges -->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

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

MCP Protocol Conformance: common questions

Is MCP Protocol Conformance MCP server safe?
Yes, by our scan: it is graded A (86/100). Read the MCP Protocol Conformance safety report
How do I install MCP Protocol Conformance?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does MCP Protocol Conformance need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is MCP Protocol Conformance maintained?
The last commit was 4 days ago (2026-11-01). The latest release is v0.2.2.
How does MCP Protocol Conformance compare with other MCP servers?
safety score 86/100 (higher than 72% of 48,243 servers); tools 5 (the typical server has 7); tools that change things 100% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

More from studiomeyer.io →