$ loading_
Analyze local TS/JS repo dependencies and change impact before editing code.
This MCP tool appears to analyze dependency graphs and blast radius for local TypeScript/JavaScript repositories, with no required secrets and no declared remote endpoints. Given the official registry listing, open-source availability, and recent maintenance, overall risk is relatively low; however, it still has inherent local code-execution-related and repository access capabilities that warrant normal caution.
The materials explicitly state that no secrets or environment variables are required. No API tokens, account credentials, or other sensitive authentication data are requested, so credential exposure and abuse risk appears low.
No remote endpoints or external service connections are declared in the materials, and the described functionality is limited to local repository analysis. Based on the available facts, there is no clear user data egress path.
The system flags this tool as executes-code, indicating it can execute code locally or launch related processing workflows. This is a common inherent capability for MCP tools, but it still means the runtime environment and accessible directories should be constrained.
Its stated purpose is to analyze dependency relationships and blast radius in local TypeScript/JavaScript repositories, so it necessarily needs read access to the target repository files and project structure. The current materials do not show excessive access beyond that scope, but local codebase contents will be processed by the tool.
Positive factors include the official registry source, open-source code, and updates within the last year. Points to watch are the missing README, undeclared license, and very low community adoption (0 stars), which reduce audit context and maturity confidence, but do not by themselves constitute a high-risk red flag.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "io.github.vk0dev/code-impact-mcp" MCP server from askskill: Run: claude mcp add 'io-github-vk0dev-code-impact-mcp' -- npx -y @vk0/code-impact-mcp
Analyze the dependency graph for src/auth/session.ts in this TypeScript repository and explain which modules, APIs, or features may be affected if I change it. Group the results into direct and indirect impact.
A dependency graph plus a categorized list of impacted modules and risks to estimate change scope.
Find the critical dependency paths from src/api/orders.ts to payment-related modules, and mark the core files along the way so I can understand the coupling between order features and payment logic.
Critical dependency paths with explanations of core nodes to quickly understand module coupling.
I’m planning to refactor the utils directory. Analyze which modules reference it, how broad the impact is, and identify the files or entry points that should get tests first.
References to the utils directory, its blast radius, and recommended high-priority test targets.
Analyze dependency graphs to predict breaking changes and enforce provenance safeguards.
Index codebases into Neo4j for analysis, dependency mapping, and impact assessment.
Scan dependencies for vulnerabilities and breaking changes with AI-powered impact analysis.
Index a monorepo into a graph for fast code structure queries.
Analyze TypeScript types and dependency graphs to understand and refactor codebases.
Build a searchable code graph so AI agents can understand repositories precisely.