Tool
change_impact
1 published MCP server declares change_impact. code-atlas has the highest trust score right now. Servers describe it as: Blast radius of a change: transitive callers + import reachability, affected test files first. Target a symbol, a file list, or nothing — no args analyzes the uncommitted git diff (hunk-level: only symbols you actually touched seed the trav Few published servers use this exact name, so read each listing before you install. Open a server for its install config and the rest of its tools.
50Trust score 50 of 100, Fair
Code intelligence MCP: symbols, call graphs, change impact + affected tests, routes, search.
Registry
FAQ
- What is the change_impact MCP tool?
- change_impact is a tool name MCP servers declare. A description they publish is: Blast radius of a change: transitive callers + import reachability, affected test files first. Target a symbol, a file list, or nothing — no args analyzes the uncommitted git diff (hunk-level: only symbols you actually touched seed the trav
- Which MCP servers provide change_impact?
- 1 published server declares change_impact. Highest in the current trust order: code-atlas.
- How do I use change_impact?
- Install a server that declares change_impact, then call it from Claude, Cursor, or VS Code. Each server page has the config for that client and the other tools that server exposes.