change_impact

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

Every row is point-in-time scan output, dated below. Forge has an observed tool surface for 12,442 of 40,855 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. @bashbop/otitoMCPattestedtrust 85/100 · A

   v3.3.0

   ↓ 548/wk

   ★ 2

   Deterministic local repository context, impact analysis, and merge-readiness evidence for AI agents.

   ClaudeCursorCopilotGemini

   io.github.BASHBOPMIT16d agonpmGitHub+compareobserved 2026-08-13 · static extraction

   mcp
2. @nugehs/repoctxMCPattestedtrust 85/100 · A

   v2.6.0

   Local-first code context, impact analysis, and merge-readiness verdicts for AI agents.

   ClaudeCursorCopilotGemini

   io.github.nugehsUnknown2mo agonpmGitHub+compareobserved 2026-06-14 · static extraction

   mcp
3. weavatrix-jsMCPattestedtrust 85/100 · A

   v0.3.15

   Always-fresh local repo graph: LSP-backed impact, Health, dead code, endpoints, architecture.

   ClaudeCursorCopilotGemini

   io.github.sergii-ziborovUnknown2mo agonpmGitHub+compareobserved 2026-08-18 · static extraction

   mcp
4. @lusiem/code-atlasMCPcommunitytrust 60/100 · B

   v0.5.0

   Code intelligence MCP: symbols, call graphs, change impact + affected tests, routes, search.

   ClaudeCursorCopilotGemini

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

   mcp

All indexed toolsSearch the registry for change_impact