io.studiomeyer/protocol-conformance

Name: io.studiomeyer/protocol-conformance
Rating: 60 (1 reviews)
Author: io.studiomeyer

MCPcommunity

v0.1.1io.studiomeyerUnknownUpdated 2mo agonpm GitHub

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

Part of the StudioMeyer MCP Stack — Built in Mallorca 🌴 · ⭐ if you use it 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…

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →

2mo agoLast update

Package

Authorio.studiomeyer

LicenseUnknown

Version0.1.1

Sourcemcp-registry

npmmcp-protocol-conformance

GitHubstudiomeyer-io/mcp-protocol-conformance

Trust Status

60/100Good

✓Listed in Forge index+10/10

—Publisher identity verified+0/25

→ Publisher: run `forge publish` from the package repo to claim ownership

—Ed25519 publish signature+0/10

→ 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>" }

✓CVE scan · clean+30/30

✓Static analysis · clean+20/20

—npm provenance (Sigstore)+0/5

→ Publish from GitHub Actions with the --provenance flag

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.0 · 20d ago

EvalsNone

IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts — it cannot prove the absence of malicious code.

About

Keywords

mcp