mcp-protocol-conformance

MCPcommunity
v0.2.1Matthias MeyerMITUpdated 1mo agonpmGitHub

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

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
97Downloads/wk
1mo agoLast update
Package
AuthorMatthias Meyer
LicenseMIT
Version0.2.1
Sourcenpm+mcp-registry
npmmcp-protocol-conformance
GitHubstudiomeyer-io/mcp-protocol-conformance
SBOMCycloneDX 1.6 ↓
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface12 tools · none privileged
Security scan✓ Cleanv0.2.1 · 1mo agoHow well does this scan work?
EvalsNone
IndexedAug 20, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

12 tools · none privileged
Statically extracted from the published packagev0.2.1 · 1mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

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

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

No input schema was published for this tool.

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

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

No input schema was published for this tool.

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

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

No input schema was published for this tool.

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

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

No input schema was published for this tool.

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

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

No input schema was published for this tool.

runCapabilityIntrospectionCompare the capabilities the target advertises in initialize against what tools/list, resources/list, prompts/list actually return.

Compare the capabilities the target advertises in initialize against what tools/list, resources/list, prompts/list actually return.

No input schema was published for this tool.

runRoundtripSmokePerform one tools/call per advertised tool. Fails on JSON-RPC transport errors, warns on tool-level isError=true.

Perform one tools/call per advertised tool. Fails on JSON-RPC transport errors, warns on tool-level isError=true.

No input schema was published for this tool.

runAnnotationsAuditApply the heuristic annotation rules (destructive name regex, readOnlyHint conflicts) to every advertised tool.

Apply the heuristic annotation rules (destructive name regex, readOnlyHint conflicts) to every advertised tool.

No input schema was published for this tool.

runFullSuiteRun all (or selected) suites and produce a FullReport with summary + per-suite + per-check status.

Run all (or selected) suites and produce a FullReport with summary + per-suite + per-check status.

No input schema was published for this tool.

generateReportRender a FullReport as JUnit XML, JSON, or human-readable terminal output.

Render a FullReport as JUnit XML, JSON, or human-readable terminal output.

No input schema was published for this tool.

compareManifestsDiff two tool manifests — added/removed/changed tools.

Diff two tool manifests — added/removed/changed tools.

No input schema was published for this tool.

assertNoBreakingChangesCompare a baseline FullReport against a current FullReport. Returns a list of breaking changes and warnings.

Compare a baseline FullReport against a current FullReport. Returns a list of breaking changes and warnings.

No input schema was published for this tool.

12 of 12 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

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

Keywords
mcpmodel-context-protocolconformancevalidatortest-harnessjson-rpcoauthpkce
Alternatives
Comparing tool surfaces…

Tools exposed

12 tools · none privileged · observed by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

Dependency tree

What one Forge scan resolved from npm metadata on 2026-08-30 — observed resolution, not a publisher declaration.

60 packages resolved · 6 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

56 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

+44 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.

Topics

Related in testing & ci