mcp-protocol-conformance
Related Servers
Alternatives to mcp-protocol-conformance
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables building and testing Model Context Protocol servers with a decorator-based API, in-process JSON-RPC test client, and 14-check protocol conformance report.MIT
- AlicenseNot gradedqualityDmaintenanceA comprehensive reference implementation demonstrating all features of the Model Context Protocol (MCP) specification, serving as documentation, learning resource, and testing tool for MCP implementations.1MIT
- AlicenseNot gradedqualityDmaintenanceModel Context Protocol server that standardizes tool discovery, execution, and context management for AI applications.MIT
- AlicenseNot gradedqualityDmaintenanceA TypeScript-based test implementation for the Model Context Protocol (MCP) with example configurations and Jest test cases. Provides a development foundation for building and testing MCP server functionality.MIT
- AlicenseNot gradedqualityDmaintenanceModel Context Protocol server that enables API test automation across various AI hosts (Claude, OpenAI, custom) using Postman Collections.MIT
- AlicenseNot gradedqualityDmaintenanceA comprehensive testing server for validating MCP scanner tools and implementations, providing diverse tools, resources, and prompts that exercise various aspects of the Model Context Protocol specification.MIT
TDQS
Scored across 12 tools
Each tool targets a distinct conformance concern: JSON-RPC framing, spec version, transport, OAuth, schema shape, capability consistency, roundtrip, annotations, manifest diffing, and report rendering. runFullSuite intentionally aggregates the others but is clearly described as an orchestrator rather than a duplicate check. No two tools appear to do the same thing.
Nine tools share the runXSuite/runXAssertion camelCase verb_noun pattern, and the remaining three use equally descriptive distinct verbs (generateReport, compareManifests, assertNoBreakingChanges) that signal post-processing rather than test execution. The convention is predictable, though the run-prefix is applied to a few tools that are checks rather than suites.
Twelve tools is well within the ideal range and each maps to a concrete, non-redundant conformance check or reporting step. Nothing feels padded, and the granular suite tools plus a full-suite orchestrator is a natural decomposition.
The surface covers the major conformance axes: JSON-RPC, transport, spec version, OAuth PKCE, tool schemas, capability introspection, roundtrips, annotations, reporting, and regression detection. Gaps remain for server-initiated features (sampling, roots, elicitation), notification/progress behavior, and non-PKCE auth methods, but these are extensions rather than dead ends.