MCP Tools DirectoryAbout this integration
MCP conformance test harness. JSON-RPC, OAuth 2.1 PKCE, schemas, smoke, annotations. CLI + lib.
- Transport
- stdio
- Authentication
- unknown
- Initial setup
- unknown
- Runtime
- unattended
- Evidence
- documented
- Version
- 0.2.1
- Package
- mcp-protocol-conformance
- Last compatibility test
- Not independently tested
Connect your agent
mcp-protocol-conformancePublisher README and package manifest reviewed offline. The harness and any target server were not executed, and no conformance result is asserted here. OAuth and authorization-header documentation concerns tested targets, not proven authentication for this local server. Existing catalog identity and connection are retained.
Capabilities: MCP protocol conformance checks, Transport and schema validation, OAuth PKCE flow checks, Manifest comparison and breaking-change checks
Connected profiles
Additional details
io.studiomeyer/protocol-conformance
Source ↗ · Checked 2026-09-170.2.1
Source ↗ · Checked 2026-09-17CC0-1.0; package licenses are separate
Source ↗ · Checked 2026-09-17npm
Source ↗ · Checked 2026-09-17mcp-protocol-conformance
Source ↗ · Checked 2026-09-200.2.1
Source ↗ · Checked 2026-09-20The publisher explicitly documents the harness itself as an MCP server started over stdio.
Source ↗ · Checked 2026-09-20The publisher does not document authentication for the harness's own local stdio server. Its token and OAuth examples configure servers under test, so the harness authentication classification remains unknown.
Source ↗ · Checked 2026-09-20Local stdio connection launched with node dist/server.js; the existing stdio transport and null endpoint are retained.
Source ↗ · Checked 2026-09-20Publisher documentation reviewed; package and integration endpoint not executed or independently security-audited.
Source ↗ · Checked 2026-09-20