mcp-spec-compliance-mcp
Related Servers
Alternatives to mcp-spec-compliance-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceAudits any MCP server (stdio or Streamable HTTP, legacy or modern era) with wire-level conformance, security, and behavior-regression checks, producing a fingerprinted delivery report and CI regression suite.1MIT
- AlicenseAqualityBmaintenanceA stdio MCP server that audits other MCP servers over the live protocol. It connects to any MCP target (stdio or HTTP), lints every tool's schema for agent-usability, then actually calls the tools with deliberately broken inputs to see how the server handles them, and returns a 0–100 conformance score with a per-dimension breakdown rendered as Markdown.620 npm6MIT
- AlicenseNot gradedqualityAmaintenanceAudits MCP server configurations for security risks including capability inventory, SSRF, prompt injection, and drift detection. Works in read-only mode and can also be used as an MCP server to let AI agents audit their own attack surface.259 PyPI4MIT
- AlicenseAqualityDmaintenanceA stdio MCP server that audits other MCP servers by linting their tool schemas and calling tools with malformed inputs to produce a 0–100 conformance score and Markdown report.620 npmMIT
- AlicenseNot gradedqualityCmaintenanceA security linter for MCP that audits other MCP servers for compliance with the MCP specification and OWASP security standards, providing detailed findings and remediation.1MIT
- AlicenseNot gradedqualityDmaintenanceSecurity auditor for MCP servers that enumerates tools, resources, and prompts, scans for injection patterns, classifies risk levels, and produces a scored report (0-100, grades A-F).31 PyPI2MIT
TDQS
Scored across 6 tools
audit_server_json substantially overlaps with check_required_fields and check_naming_conventions, since the former is effectively a superset of the two fast gates. However, descriptions clearly frame the latter as lightweight gates, so an agent can reasonably choose between them.
Every tool follows a consistent snake_case verb_noun pattern (audit_server_json, check_required_fields, list_spec_versions, generate_passing_template, sign_conformity_report). No deviations in style or casing.
Six tools is well-scoped for a compliance/linting server, covering audit, fast checks, version lookup, template generation, and signing. Each tool earns its place without redundancy.
The surface covers the full audit-to-evidence lifecycle (check, audit, template, sign) and is largely self-contained. Minor gaps exist, such as no explicit schema-field-level validator or fix/repair operation, but agents can work around these.