# mcp-protocol-conformance

Conformance test harness for Model Context Protocol servers. Validates JSON-RPC 2.0, spec-version handshake, transport, OAuth 2.1 PKCE, tool schemas, capabilities, smoke roundtrip, and annotations against MCP spec 2024-11-05 / 2025-03-26 / 2025-06-18 / 20

- **Type:** MCP server
- **Trust:** 60/100 (B), scored on the package rubric
- **Verification:** community-indexed — nobody has claimed this listing
- **Version:** 0.2.1
- **Author:** Matthias Meyer
- **License:** MIT
- **npm:** mcp-protocol-conformance
- **Source:** https://github.com/studiomeyer-io/mcp-protocol-conformance
- **Compatible clients:** claude-code, cursor, copilot, gemini (basis: transport)

## Trust

60/100 (B), scored on the package rubric
- Publisher verified: no
- Install scripts: nothing suspicious found
- Prompt-injection scan: not run
- Obfuscation scan: not run
- Evidence age: 3 days

## Security scan

- **Status:** clean
- **Scanned:** 2026-08-30T17:26:11.039Z
- **Version scanned:** 0.2.1
- **CVEs:** none found by OSV at scan time

## Tools

12 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `runJsonRpcCompliance` — Run JSON-RPC 2.0 compliance suite (parse-error, invalid-request, method-not-found, invalid-params, internal-error) against a target MCP server.
- `runSpecVersionAssertion` — Drive an initialize handshake and assert the target advertises the expected MCP spec version.
- `runTransportSuite` — Verify the target's transport layer (stdio line-delimited JSON or Streamable HTTP).
- `runOauthPkceFlow` — Exercise OAuth 2.1 PKCE S256 flow against the target. Mock-AS by default; real-tenant when --oauth-mode=real.
- `runToolSchemaValidation` — Validate that every advertised tool has a well-formed JSON-Schema inputSchema. Optionally diff against an expected manifest.
- `runCapabilityIntrospection` — Compare the capabilities the target advertises in initialize against what tools/list, resources/list, prompts/list actually return.
- `runRoundtripSmoke` — Perform one tools/call per advertised tool. Fails on JSON-RPC transport errors, warns on tool-level isError=true.
- `runAnnotationsAudit` — Apply the heuristic annotation rules (destructive name regex, readOnlyHint conflicts) to every advertised tool.
- `runFullSuite` — Run all (or selected) suites and produce a FullReport with summary + per-suite + per-check status.
- `generateReport` — Render a FullReport as JUnit XML, JSON, or human-readable terminal output.
- `compareManifests` — Diff two tool manifests — added/removed/changed tools.
- `assertNoBreakingChanges` — Compare a baseline FullReport against a current FullReport. Returns a list of breaking changes and warnings.

## Install

**Verdict: review** — Installable, but 1 thing to check first: No publisher has proved control of this listing; it is indexed, not vouched for.
**Cautions** (coverage gaps and advisories — never blocking)
- No publisher has proved control of this listing; it is indexed, not vouched for.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"mcp-protocol-conformance\": {\n      \"command\": \"npx\",\n      \"args\": [\n        \"-y\",\n        \"mcp-protocol-conformance\"\n      ]\n    }\n  }\n}"
```

## Blast radius

Contained to moderate — no credential declaration found, from the publisher, the upstream registry, or the README. Known so far: runs on your machine; read-only tool surface.
- Floor 13, ceiling 31 (tier: unknown)
- `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low.
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/mcp-protocol-conformance
- Install plan: https://forgeregistry.com/api/v1/packages/mcp-protocol-conformance/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/mcp-protocol-conformance
- HTML page: https://forgeregistry.com/registry/mcp-protocol-conformance
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.