About io.github.vola-trebla/release-readiness-triage-mcp
io.github.vola-trebla/release-readiness-triage-mcp is an MCP server in the Science category: aggregates CI failures, cross-references flakiness history, and outputs GO/NO_GO release verdicts.
Install
claude mcp add io-github-vola-trebla-release-readiness-triage-mcp -- npx -y release-readiness-triage-mcpnpx -y release-readiness-triage-mcpThis server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.
Tools (6)
aggregate_suite_failuresParse a CI test run and group failures by error signature. Deduplicates repeated errors and categorizes them as assertion, timeout, network, or crash. Use this as the first step before triage.
Parameters not published.
analyze_rollback_readinessScans a repository for versioned database migration files (Flyway V*.sql, Prisma migration.sql, Liquibase XML/YAML) and classifies each operation as additive (rollback safe) or destructive (forward-fix only). Returns rollback_eligible, a list of blocking_migrations with file and line, and deployment_strategy. Use before recommending deployment to determine whether a rollback is safe after go-live.
Parameters not published.
correlate_code_changesMatch a list of changed files against failing tests to determine which failures are directly caused by the code changes in this commit. Returns a correlation mapping.
Parameters not published.
cross_reference_flakinessGiven a list of test failures and a flakiness history, score each failure by how likely it is to be a known flaky test vs a real regression. Returns probability scores per test.
Parameters not published.
detect_temporal_failure_patternsAnalyzes a history of test failures with timestamps to detect chronometric patterns: failures that cluster at the same UTC hour (hourly jobs), same day of month (billing runs), same weekday (scheduled jobs), or around DST transitions. When a pattern is found, the failure is a time artifact — not a code regression. The agent should schedule a re-run at a different time rather than investigating the source code.
Parameters not published.
generate_release_recommendationThe final step: combines failures, flakiness history, and code change correlation to produce a GO / NO_GO / INVESTIGATE verdict with confidence score and a breakdown of blockers vs safe-to-ignore failures.
Parameters not published.
Ask AI
Ask AI about io.github.vola-trebla/release-readiness-triage-mcp
Powered by Claude · Grounded in docs
Security checks
6 checks have not been run yet.