# io.github.vola-trebla/release-readiness-triage-mcp (npm · release-readiness-triage-mcp)

Aggregates CI failures, cross-references flakiness history, and outputs GO/NO_GO release verdicts.

- Trust score: 68/100 (medium)
- Change this week: +22
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- npm · `release-readiness-triage-mcp`: 68/100 (this document), [markdown](https://verifymcp.io/servers/vola-trebla-release-readiness-triage-mcp/release-readiness-triage-mcp.md), [page](https://verifymcp.io/servers/vola-trebla-release-readiness-triage-mcp/release-readiness-triage-mcp)

## Channel facts

- Registry: `npm`
- Package: `release-readiness-triage-mcp`
- Version: `0.2.0`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Supply Chain Security**: 86/100
  - No malware found by supply-chain analysis.
  - Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree.
  - No install/post-install scripts declared.
  - Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 74 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 75/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 761 tokens (~126/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add vola-trebla-release-readiness-triage-mcp -- npx -y release-readiness-triage-mcp
```

### Codex

```bash
codex mcp add vola-trebla-release-readiness-triage-mcp -- npx -y release-readiness-triage-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "vola-trebla-release-readiness-triage-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "release-readiness-triage-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add vola-trebla-release-readiness-triage-mcp --command npx --arg -y --arg release-readiness-triage-mcp
```

### Hermes

```yaml
mcp_servers:
  vola-trebla-release-readiness-triage-mcp:
    command: "npx"
    args: ["-y", "release-readiness-triage-mcp"]
```

### Other

```json
{
  "mcpServers": {
    "vola-trebla-release-readiness-triage-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "release-readiness-triage-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 68, +3)

- [functional improvement] Stability: unverified → 0.23

### 2026-08-02 (score 65, +30)

- [security regression] Provenance: unverified → fail
- [security improvement] Known CVEs: unverified → partial
- [security improvement] Install scripts: unverified → pass
- [security] Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window).
- [functional regression] Tool coverage: 100 → unverified
- [functional improvement] Schema quality: unverified → excellent
- [functional improvement] License: unverified → pass
- [functional improvement] Dependency health: unverified → partial
- [functional improvement] Maintenance: unverified → pass
- [functional improvement] MCP protocol: unverified → pass
- [functional] Licence: MIT

### 2026-08-01 (score 35, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-07-31 (score 20, −4)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-28 (score 24, −22)

- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-07-27 (score 46)

First indexed and scored.

## MCP tools (6)

### `aggregate_suite_failures` (~167 tokens)

Parse 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.

Input parameters:

- `branch` (string): Branch name
- `commitSha` (string): Commit SHA
- `customInfraPatterns` (array): Extra regex patterns (as strings) to classify as infrastructure errors, e.g. cloud-provider-specific messages like 'No space left on device' or 'GCP quota exceeded'
- `failures` (array, required): List of test failures from the CI run
- `passedTests` (integer, required): Number of tests that passed
- `runId` (string): CI run identifier
- `totalTests` (integer, required): Total number of tests in the run

### `cross_reference_flakiness` (~94 tokens)

Given 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.

Input parameters:

- `failures` (array, required): Failures to evaluate
- `flakinessHistory` (array, required): Historical flakiness data — testName, suiteName, flakyProbability (0–1), recentFailures, totalRuns

### `correlate_code_changes` (~96 tokens)

Match 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.

Input parameters:

- `affectedTests` (array): Optional: test names already known to be affected (e.g. from ast-impact-mapper-mcp)
- `changedFiles` (array, required): List of file paths changed in this commit/PR
- `failures` (array, required): Failures to correlate against

### `generate_release_recommendation` (~186 tokens)

The 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.

Input parameters:

- `affectedTests` (array): Tests known to be affected by code changes (from ast-impact-mapper-mcp)
- `changedFiles` (array, required): Files changed in this commit/PR
- `customInfraPatterns` (array): Extra regex patterns (as strings) to classify as infrastructure errors, e.g. 'GCP quota exceeded', 'No space left on device'
- `failures` (array, required): All failures from the CI run
- `flakinessHistory` (array, required): Flakiness history for cross-referencing
- `format` (string): Output format. Use 'markdown' for GitHub PR comments or Slack. Defaults to 'text'.

### `detect_temporal_failure_patterns` (~107 tokens)

Analyzes 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.

Input parameters:

- `failures` (array, required): Historical failure records with timestamps

### `analyze_rollback_readiness` (~111 tokens)

Scans 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.

Input parameters:

- `repo_path` (string, required): Absolute path to the repository root to scan for migration files

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/vola-trebla-release-readiness-triage-mcp/release-readiness-triage-mcp#diagnostics

## Score history

- 2026-08-03: 68
- 2026-08-02: 65
- 2026-08-01: 35
- 2026-07-31: 20
- 2026-07-30: 24
- 2026-07-28: 24
- 2026-07-27: 46

## Links

- npm package: https://www.npmjs.com/package/release-readiness-triage-mcp
- Socket report: https://socket.dev/npm/package/release-readiness-triage-mcp
- Repository: https://github.com/vola-trebla/release-readiness-triage-mcp
- Changelog RSS feed: https://verifymcp.io/servers/vola-trebla-release-readiness-triage-mcp/release-readiness-triage-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/vola-trebla-release-readiness-triage-mcp/release-readiness-triage-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/vola-trebla-release-readiness-triage-mcp/release-readiness-triage-mcp