release_readiness

3 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 12,342 of 40,590 scannable entries (30%) — 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-serverMCPattestedlivetrust 85/100 · A

   v2.7.4

   ↓ 11k/wk

   ★ 32

   Official MCP server for Qase — manage test cases, runs, suites, defects via AI tools.

   ClaudeCursorCopilotChatGPTGemini

   io.qaseMIT17d agonpmGitHub+compareobserved 2026-10-12 · static extraction

   mcp
2. @abd3lraouf/app-store-connect-mcpMCPattestedtrust 85/100 · A

   v1.3.0

   App Store Connect + StoreKit 2: 1,293 Apple operations behind 11 tools, writes confirmed.

   ClaudeCursorCopilotGemini

   io.github.abd3lraouf-studiosUnknown1mo agonpmGitHub+compareobserved 2026-09-01 · static extraction

   mcp
3. mcp-zebrunnerMCPcommunitytrust 60/100 · B

   v9.2.1

   Advanced analytics, reporting, and safe mutations for Zebrunner. 64 tools, 14 resources, 17 prompts.

   ClaudeCursorCopilotGemini

   io.github.maksimsarychauUnknown3mo agonpmGitHub+compareobserved 2026-08-14 · static extraction

   mcp

All indexed toolsSearch the registry for release_readiness