Skip to main content
Glama

Related Servers

Alternatives to code-relay-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      Enables coding agents to identify the least-proven claim in code after edits and receive a focused repair packet with exact source anchors, missing proof, reproducer, and a done condition, supporting iterative verify/fix loops.
      3
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding agents to keep persistent, verifiable memory of a codebase, including the reasons behind code, prior rejected approaches, and invariants, anchored to the code and carried along as the code moves.
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables host coding agents to conduct evidence-first exploratory testing, adversarial review, reproduction, and resumable reporting through immutable job contracts, action budgets, checkpointed ledgers, integrity-checked artifacts, and optional origin-restricted browser automation.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding agents to scaffold, verify, audit, and safely modify software projects across 11 technology stacks, with rollback checkpoints, session continuity, and an evidence-based learning loop.
      64 npm
      MIT

    TDQS

    B3/5.0

    Scored across 10 tools

    Disambiguation4/5

    Most tools target distinct actions and resources, such as bind_project, publish_runbook, and fetch_receipt. The main ambiguity is between status and watcher_status, though their descriptions clarify that one covers runbook/receipt status and the other legacy watcher state.

    Naming Consistency3/5

    Most tools follow a verb_noun pattern like create_checkpoint_invite and publish_runbook. However, doctor and status are bare nouns, and analyze is a bare verb, creating a mixed convention that is readable but not consistently patterned.

    Tool Count5/5

    With 10 tools, the server is well-scoped for its domain. Each tool appears to cover a meaningful part of the project binding, checkpoint, and runbook workflow without unnecessary bloat.

    Completeness3/5

    The runbook and receipt workflow is well covered with publish, status, fetch, and analyze. However, lifecycle gaps exist: there is no unbind_project, no checkpoint leave/revoke tool, and no way to start the legacy watcher, only to stop it.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues