DeployAngel
Related Servers
Alternatives to DeployAngel
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables 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.1 npmApache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables 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.0MIT
- AlicenseNot gradedqualityCmaintenanceProvides 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.416 npmMIT
- AlicenseAqualityAmaintenanceChecks claims in AI agent reports — quotations, numbers, repo anchors, PR/CI status, and 'I ran it' outputs — against primary evidence such as byte snapshots, repository bytes, the GitHub API and session transcripts, with no model in the loop. Every check returns a re-runnable receipt and a non-zero exit code on failure, so a wrong quote or invented test result can be blocked at any hand-off.4Apache 2.0
- AlicenseAqualityBmaintenanceChecks what local coding agents such as Claude Code, Codex and Cursor really did: files changed, commands run and test results read from test output, not the agent's word. Unclear test results can be double-checked by Laya (on your computer) or TypeSafe's Jev (cloud, your own API key). Read-only.21093 npm53MIT
- AlicenseNot gradedqualityDmaintenanceRead-only MCP server for Jenkins CI, enabling AI agents to securely query job/build status, logs, artifacts, and generate verification reports for loop workflows.17 npmISC
TDQS
Scored across 6 tools
get_verification (immediate snapshot) and wait_for_verification (blocking poll) are functionally distinct, and the remaining tools target clearly separate resources: deployments list, exercise plan, exception details, and post-clearance regressions. There is mild overlap between get_verification and wait_for_verification since both return the same verdict document, but descriptions clarify the difference.
All six tools follow a clean verb_noun snake_case pattern (get_*, wait_for_*, list_*), with verbs matching their action type consistently. No convention mixing.
Six tools is well-scoped for a deployment verification/monitoring server, with each tool earning its place in the verification workflow.
Coverage is strong for the verification domain: read state, wait for verdict, plan exercises, list deployments, inspect exceptions, and track late regressions. However, the exercise-plan description references a 'report_with' tool for reporting runs that is not present, creating a minor dead end.