Skip to main content
Glama
zegroged

vacuous-tests-mcp

by zegroged
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to vacuous-tests-mcp

No user-submitted related servers found.

    Related Servers

    • openhonest-umbra by openhonest

      openhonest-umbraofficial

      openhonest
      A
      license
      A
      quality
      A
      maintenance
      Audits a module against its test suite and reports the cases the tests are structurally unable to see, then proves each gap with a real failing test rather than a warning. Covers Python, TypeScript, JavaScript, Java, Rust and Go.
      4
      3
      Apache 2.0
    • faultline by Energixe

      faultlineofficial

      Energixe
      A
      license
      Not graded
      quality
      B
      maintenance
      Generates complete runnable adversarial test suites for your code, predicting the bugs they expose with exact code evidence, across multiple languages and test frameworks.
      MIT

    • Momus-MCP

      AraneaDev
      A
      license
      Not graded
      quality
      A
      maintenance
      A local-first, deterministic, read-only MCP server that audits test suites for false-green tests, tautological assertions, and mock-contract drift, ensuring tests truly validate production code. It provides tools to detect test fidelity issues, verify mock drift, and synthesize strict mock contracts.
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.2/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a distinct purpose: listing available rules, explaining a specific rule, and scanning tests for vacuous assertions. There is no overlap between scan_tests and the two rule-related tools, and list_rules/explain_rule are clearly separated by verb (list vs. explain).

    Naming Consistency5/5

    All tools follow a consistent snake_case verb_noun pattern: list_rules, explain_rule, scan_tests. The naming is predictable and aligns perfectly with the tool's action.

    Tool Count5/5

    With 3 tools, the server is well-scoped for its purpose—a test scanner with rule documentation. Each tool earns its place, and the count falls squarely within the typical 3-15 range for a focused server.

    Completeness5/5

    The tool surface fully covers the intended workflow: discover rules, understand a rule, and run the scanner. There are no obvious gaps—the scanner's options are handled via arguments rather than requiring additional tools, and the rule lifecycle (list/explain) is complete for a read-only server.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources