io.github.vola-trebla/release-readiness-triage-mcp

MCPcommunity
v0.2.0io.github.vola-treblaUnknownUpdated 1mo agonpmGitHub

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

Stop reading CI logs. Start getting verdicts. MCP server that aggregates test failures, cross-references flakiness history, and outputs a GO / CONDITIONALGO / NOGO / 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. In any real codebase, CI always has something failing. The hard question isn't "are there…

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
1mo agoLast update
Package
Authorio.github.vola-trebla
LicenseUnknown
Version0.2.0
Sourcemcp-registry
npmrelease-readiness-triage-mcp
GitHubvola-trebla/release-readiness-triage-mcp
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/25
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/10
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
—npm provenance (Sigstore)+0/5
→ Publish from GitHub Actions with the --provenance flag
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface6 tools · none privileged
Security scan✓ Cleanv0.2.0 · 20d ago
EvalsNone
IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts — it cannot prove the absence of malicious code.

About

Stop reading CI logs. Start getting verdicts. MCP server that aggregates test failures, cross-references flakiness history, and outputs a GO / CONDITIONALGO / NOGO / 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. 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…

Keywords
mcp