io.github.vola-trebla/release-readiness-triage-mcp
NPM · RELEASE-READINESS-TRIAGE-MCP · SCANNED AUG 3
Aggregates CI failures, cross-references flakiness history, and outputs GO/NO_GO release verdicts.
Available components
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. How we score →
Supply Chain Security86
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 74 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability75
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · release-readiness-triage-mcp
claude mcp add vola-trebla-release-readiness-triage-mcp -- npx -y release-readiness-triage-mcp
codex mcp add vola-trebla-release-readiness-triage-mcp -- npx -y release-readiness-triage-mcp
{
"$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 mcp add vola-trebla-release-readiness-triage-mcp --command npx --arg -y --arg release-readiness-triage-mcp
mcp_servers:
vola-trebla-release-readiness-triage-mcp:
command: "npx"
args: ["-y", "release-readiness-triage-mcp"] {
"mcpServers": {
"vola-trebla-release-readiness-triage-mcp": {
"command": "npx",
"args": [
"-y",
"release-readiness-triage-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Aug 26 +3
- Stability: unverified → 0.23 ▲ functional
- 2 Aug 26 +30
- Provenance: unverified → fail ▼ security
- Known CVEs: unverified → partial ▲ security
- Install scripts: unverified → pass ▲ security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: unverified → excellent ▲ functional
- License: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- Maintenance: unverified → pass ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Licence: MIT functional
- 1 Aug 26 +15
- Malware scan: unverified → pass ▲ security
- 31 Jul 26 −4
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 28 Jul 26 −22
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 27 Jul 26 46
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 3 Aug 2026 · Analysed npm/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 94 packages
94 packages in the resolved dependency tree · 94 deprecated · 29 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
aggregate_suite_failures ~167
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | List of test failures from the CI run |
| passedTests | integer | yes | Number of tests that passed |
| runId | string | — | CI run identifier |
| totalTests | integer | yes | Total number of tests in the run |
No output schema declared.
No examples provided.
analyze_rollback_readiness ~111
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.
| Name | Type | Req | Description |
|---|---|---|---|
| repo_path | string | yes | Absolute path to the repository root to scan for migration files |
No output schema declared.
No examples provided.
correlate_code_changes ~96
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.
| Name | Type | Req | Description |
|---|---|---|---|
| affectedTests | array | — | Optional: test names already known to be affected (e.g. from ast-impact-mapper-mcp) |
| changedFiles | array | yes | List of file paths changed in this commit/PR |
| failures | array | yes | Failures to correlate against |
No output schema declared.
No examples provided.
cross_reference_flakiness ~94
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.
| Name | Type | Req | Description |
|---|---|---|---|
| failures | array | yes | Failures to evaluate |
| flakinessHistory | array | yes | Historical flakiness data — testName, suiteName, flakyProbability (0–1), recentFailures, totalRuns |
No output schema declared.
No examples provided.
detect_temporal_failure_patterns ~107
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.
| Name | Type | Req | Description |
|---|---|---|---|
| failures | array | yes | Historical failure records with timestamps |
No output schema declared.
No examples provided.
generate_release_recommendation ~186
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.
| Name | Type | Req | Description |
|---|---|---|---|
| affectedTests | array | — | Tests known to be affected by code changes (from ast-impact-mapper-mcp) |
| changedFiles | array | yes | 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 | yes | All failures from the CI run |
| flakinessHistory | array | yes | Flakiness history for cross-referencing |
| format | string | — | Output format. Use 'markdown' for GitHub PR comments or Slack. Defaults to 'text'. |
No output schema declared.
No examples provided.