Skip to main content
Glama

Related Servers

Alternatives to siftwise

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for test impact analysis and code intelligence. Maps tests to code and git history to determine impacted tests, risk scores, and ownership for AI coding agents.
      8
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Content-addressed code graph that produces ranked context for AI agents in one call. 22 MCP tools across indexing, blast radius, test scope, semantic diff, runtime traffic, and feedback-aware context packing. Incremental updates via Merkle DAG (no re-indexing). GCF wire format saves 84% tokens vs JSON
      24
      Apache 2.0
    • A
      license
      A
      quality
      B
      maintenance
      Agentic DevOps control loop and MCP server featuring polyglot Tree-sitter AST blast-radius analysis, OPA Rego policy evaluation, and isolated --network=none Docker test verification[cite: 1]. Exposes tools to inspect impacted dependency closures, validate security guardrails, and run targeted test suites.
      3
      2
      Apache 2.0

    TDQS

    A4/5.0

    Scored across 3 tools

    Disambiguation5/5

    The three tools serve clearly distinct workflow stages: selecting affected tests before a run, triaging failing tests afterward, and explaining one test in detail when needed. The descriptions explicitly state when to call each, so an agent should not confuse them.

    Naming Consistency4/5

    select_tests and triage_failure follow a clear verb_noun pattern, while explain is a bare verb. The deviation is minor and readable, but it prevents a perfect consistency score.

    Tool Count4/5

    Three tools is a minimal but well-scoped set for the server's test-selection and triage purpose. Each tool earns its place, though the surface is at the low end of what feels comfortably complete.

    Completeness4/5

    The tools cover the core lifecycle: selecting tests, triaging failures, and explaining individual test behavior. Minor gaps exist around discovering/configuring test inventory or reporting outcomes, but the main workflow has no dead ends.

    Maintenance

    ActivityActive
    ResponsivenessNo recent community issues