Skip to main content
Glama

Related Servers

Alternatives to mcp-compliance

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables natural-language testing of MCP servers—covering tools, resources, prompts, contracts, and transports—without writing test code, with deterministic validation and CI integration.
      30 npm
      Apache 2.0
    • A
      license
      A
      quality
      B
      maintenance
      A specialized testing harness that enables AI assistants to thoroughly test other MCP servers by connecting to them, discovering their tools/resources/prompts, executing test calls, and performing end-to-end validation with LLM integration.
      14
      4
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      MCP server that lets coding agents test AI agents. Create YAML test cases, snapshot golden baselines, check for regressions, and generate visual reports all from inside Claude Code or any MCP-compatible tool. Works with LangGraph, CrewAI, OpenAI, Claude, Mistral, and any HTTP API.
      10
      143 npm
      2,124 PyPI
      142
      Apache 2.0
    • A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to programmatically inspect, test, and validate other MCP servers by exposing MCP Workbench capabilities as structured tools. It supports automated test spec generation, execution, and detailed failure analysis to ensure server reliability.
      4
      13 npm
      Apache 2.0
    • A
      license
      A
      quality
      B
      maintenance
      A 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.
      6
      14 npm
      6
      MIT

    TDQS

    A3.9/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct roles: one is a read-only documentation lookup for a test ID, the other executes the compliance suite against a server URL. An agent can trivially tell which to call based on whether it needs an explanation or an actual test run.

    Naming Consistency5/5

    Both tools follow the same predictable prefix_verb pattern (mcp_compliance_explain, mcp_compliance_test), with single, unambiguous verbs. No mixing of conventions or stylistic outliers.

    Tool Count4/5

    Two tools is on the thin side, but the server's purpose (run the compliance suite and explain its checks) is narrow enough that this feels deliberately scoped rather than underbuilt. No redundant or filler tools are present.

    Completeness3/5

    The core lifecycle (run tests, explain a result) is covered, but there is no way to enumerate available test IDs or list the supported spec suites, so an agent must already know an ID or discover it from a test run's output. A discovery/list operation is a notable gap for a testing tool.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data