release_readiness

2 registry entries were observed exposing a tool named release_readiness — none of them flagged as a privileged capability.

Spelled release_readiness, release-readiness in the wild — all one tool for the purposes of this page.

Every row is point-in-time scan output, dated below. Forge has an observed tool surface for 8,470 of 26,658 scannable entries (32%) — an entry that has not been scanned cannot appear here, so absence from this list is not evidence that an entry does not expose this tool.

1. @qase/mcp-serververified
   trust 85/100 · AMCP serverobserved 2026-08-10 · static extraction
   Official MCP server for Qase — manage test cases, runs, suites, defects via AI tools.
2. mcp-zebrunner
   trust 60/100 · BMCP serverobserved 2026-08-14 · static extraction
   Advanced analytics, reporting, and safe mutations for Zebrunner. 64 tools, 14 resources, 17 prompts.

All indexed toolsSearch the registry for release_readiness