Skip to main content
Glama

Related Servers

Alternatives to DeployAngel

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables evidence-first release readiness assessment by running or accepting build, API, browser, visual, performance, and security evidence, then returning SHIP, REVIEW, or HOLD recommendations with clustered regressions.
      7 npm
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables read-only diagnosis of deployment failures across AWS, Vercel, Docker, CI/CD, and application stacks by correlating project files, logs, and provider evidence into ranked findings with safe recommendations and verification steps.
      2
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables deterministic release-quality audits over a release snapshot, exposing rules and findings with evidence and severity counts. It also renders Slack Block Kit posts with an optional, clearly attributed agent narrative.
      6 npm
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      A read-only server that enables AI agents to triage Kubernetes CronJobs in a single tool call: whether runs happened and stayed on schedule, whether durations are trending slower or overrunning, which jobs have silently stopped succeeding, and why a given run failed, with evidence and stated basis for each verdict. It also lists active runs and recent failures while enforcing namespace allowlists and no write access.
      8
      52 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Provides read-only access to Jenkins, enabling users to inspect project and environment build status, list builds, retrieve console logs and test reports, diagnose failed builds, and search jobs via natural language, without triggering or changing builds.
      1,350 npm
      MIT

    TDQS

    B3.2/5.0

    Scored across 6 tools

    Disambiguation4/5

    The tools mostly target distinct resources: deployment listing, verification documents, waiting, exercise plans, exception details, and late regressions. The main possible confusion is between list_deployments, get_verification, and wait_for_verification, but the descriptions make their different roles reasonably clear.

    Naming Consistency5/5

    All tool names use snake_case and a verb-first pattern: list_*, get_*, and wait_for_*. The wait_for_verification name is slightly longer but still follows the same predictable convention.

    Tool Count5/5

    Six tools is a well-scoped set for a deployment verification server. The tools cover the main read and wait workflows without obvious padding.

    Completeness2/5

    The surface has a direct dead end: get_exercise_plan tells the agent to report what it ran with report_with, but no such tool exists. There is also no tool to record exercise runs or dismiss late regressions, so key follow-up actions implied by the descriptions cannot be completed.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data