Skip to main content
Glama

Related Servers

Alternatives to nightward

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Fail-closed merge gate for AI coding agents: verify_repo runs the tests that existed before the change against a git working tree and answers MERGE, BLOCK or INCONCLUSIVE. The agent names what to judge; the operator pins the baseline and the floors.
      2
      61 PyPI
      4
      AGPL 3.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables deterministic behavioral regression review of pull-request diffs by checking changed code against approved incident-derived contracts. It exposes read-only tools to assess diffs and pull requests, list and fetch contracts, and report outcomes over stdio without mutating repositories.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding assistants to scan a repository for code that cannot prove its usefulness, attribute it to AI-assisted or human commits, prove candidate deletions against the project's own tests, and pull a payoff report or run history, all without ever writing to the repository. The test command and any model judging stay under a person's control through environment configuration.
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Exposes 11 agent-native QA tools over stdio so coding agents can discover a project, analyze risk, select the smallest relevant test set, generate and dry-run tests, triage failures, propose tiered heals, analyze flakes, generate quality reports, and evaluate release readiness. Planning and healing tools stay read-only or propose-only, while execution defaults to dry-run, keeping agent actions safe and evidence-backed.
      MIT

    TDQS

    A4.5/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: nightward_run executes tests and produces a fresh boundary verdict, while nightward_status only reads the last run's report. The descriptions explicitly clarify the relationship and warn that status cannot see edits made after the last run. There is no meaningful overlap or risk of misselection.

    Naming Consistency4/5

    Both tools share the consistent nightward_ prefix and snake_case formatting, making them clearly part of the same server. However, nightward_run uses a verb while nightward_status uses a noun, so the pattern is consistent in namespace but not strictly verb_noun throughout.

    Tool Count4/5

    Two tools is on the thin side, but each is essential to the narrow agent-facing purpose: run the gate and read the most recent result. The server deliberately avoids duplicating human-only CLI operations, so the small surface is reasonable rather than excessive.

    Completeness5/5

    For the stated MCP purpose, the surface covers the full agent workflow: trigger a fresh test/gate run, then read the last boundary report without rerunning. Approval and review remain intentionally human-only CLI actions, so their absence is not a gap in this server's role.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues