Release Readiness Triage Mcp
Turns CI failures into structured release verdicts by correlating error signatures, flakiness history, and code changes. Exposes six tools: aggregate_suite_failures groups errors by normalized signature, cross_reference_flakiness scores against historical data, correlate_code_changes maps failures to changed files, generate_release_recommendation outputs GO/CONDITIONAL_GO/NO_GO/INVESTIGATE with risk scores and domain severity (payment, auth, billing get blocked), detect_temporal_failure_patterns finds time-based artifacts like DST or hourly flakes, and analyze_rollback_readiness scans migration files for destructive operations. Outputs markdown ready for PR comments. Works standalone or composes with flakiness-knowledge-graph-mcp and ast-impact-mapper-mcp. Reach for this when you need an AI agent to triage broken CI runs without reading thousands of lines of logs.
- tools
- 6
- transport
- STDIO
- last updated
- May 20, 2026
Tools
6 toolsPublic tool metadata for what this MCP can expose to an agent.
aggregate_suite_failuresGroups failures by normalized error signature, deduplicates repeated errors, categorizes as assertion / timeout / network / crash. Pass customInfraPatterns for cloud-specific errors.
Groups failures by normalized error signature, deduplicates repeated errors, categorizes as assertion / timeout / network / crash. Pass customInfraPatterns for cloud-specific errors.
No parameter schema in public metadata yet.
cross_reference_flakinessScores each failure against your flakiness history: KNOWN FLAKY, MILDLY FLAKY, or NO HISTORY.
Scores each failure against your flakiness history: KNOWN FLAKY, MILDLY FLAKY, or NO HISTORY.
No parameter schema in public metadata yet.
correlate_code_changesMatches changed files against failing tests. Works standalone or with pre-computed affected test lists from ast-impact-mapper-mcp.
Matches changed files against failing tests. Works standalone or with pre-computed affected test lists from ast-impact-mapper-mcp.
No parameter schema in public metadata yet.
generate_release_recommendationThe final step. Outputs a risk-weighted verdict with confidence score and full breakdown. Supports format: "markdown" for GitHub PR comments and Slack.
The final step. Outputs a risk-weighted verdict with confidence score and full breakdown. Supports format: "markdown" for GitHub PR comments and Slack.
No parameter schema in public metadata yet.
detect_temporal_failure_patternsAnalyzes historical failures with timestamps to identify chronometric artifacts — failures that only appear at the same UTC hour, weekday, day of month, or during DST transitions.
Analyzes historical failures with timestamps to identify chronometric artifacts — failures that only appear at the same UTC hour, weekday, day of month, or during DST transitions.
No parameter schema in public metadata yet.
analyze_rollback_readinessScans a repository for versioned migration files (Flyway, Prisma, Liquibase) and classifies each operation as additive (rollback safe) or destructive (forward-fix only).
Scans a repository for versioned migration files (Flyway, Prisma, Liquibase) and classifies each operation as additive (rollback safe) or destructive (forward-fix only).
No parameter schema in public metadata yet.
Sponsors
Agent CaffeineSponsoredClose your lid, come back to finished work
SnugSponsoredThe clipboard manager for the AI eraPromote your product hereReach 125k+ visitors monthly
WaxSponsoredBlock anything with supervision, without erasing your iPhonePromote your product hereReach 125k+ visitors monthly
knobsSponsoredSee your site on any phone, any day, in any languageReadme
🚦 release-readiness-triage-mcp
Stop reading CI logs. Start getting verdicts.
MCP server that aggregates test failures, cross-references flakiness history, and outputs a GO / CONDITIONAL_GO / NO_GO / INVESTIGATE release decision — so your AI agent can triage a broken CI run in seconds instead of asking you to read 3000 lines of logs.
🤔 The problem
In any real codebase, CI always has something failing. The hard question isn't "are there failures?" — it's "are these failures real regressions, or just the usual noise?"
Answering that requires correlating three signals at once:
Details
- Repository
- github.com/vola-trebla/release-readiness-triage-mcp
- Package
release-readiness-triage-mcp- Transport
- STDIO
- Registry
- MCP registry, active
More from vola-trebla
- React Render Profile Mcp2
- Playwright Trace Decoder Mcp1
- Ast Impact Mapper Mcp
- Env Secret Exposure Analyzer Mcp
- Flakiness Knowledge Graph Mcp
- Ndjson Local Log Triage Mcp
- Playwright Network Chaos Mcp
- Playwright Spatial Layout Mcp
- Sourcemap Retrace Mcp
- Tailwind Context Resolver Mcp
- Tsconfig Inheritance Flattener Mcp
- V8 Cpu Profile Decoder Mcp