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 8,635 of 26,808 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. @bashbop/otitoverified
   trust 85/100 · AMCP serverobserved 2026-08-13 · static extraction
   Deterministic local repository context, impact analysis, and merge-readiness evidence for AI agents.
2. @nugehs/repoctxverified
   trust 85/100 · AMCP serverobserved 2026-06-14 · static extraction
   Local-first code context, impact analysis, and merge-readiness verdicts for AI agents.
3. weavatrix-jsverified
   trust 85/100 · AMCP serverobserved 2026-08-18 · static extraction
   Always-fresh local repo graph: LSP-backed impact, Health, dead code, endpoints, architecture.
4. @lusiem/code-atlas
   trust 60/100 · BMCP serverobserved 2026-08-14 · static extraction
   Code intelligence MCP: symbols, call graphs, change impact + affected tests, routes, search.

All indexed toolsSearch the registry for change_impact