Code Impact MCP server
Dependency graph and blast-radius analysis for local TypeScript/JavaScript repos.
1 stars66 downloads/wk
Reviews
Write oneNobody has reviewed Code Impact yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Code Impact tools (5)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
analyze_impactAnalyze the blast radius of changing specific files. Returns which files would be
detect_cyclesReturn strongly connected components with more than one file from the current dependency graph.
gate_checkPre-commit safety gate. Analyzes specified changes and returns a PASS/WARN/BLOCK
get_dependenciesGet the import and importedBy relationships for a specific file. Shows what this file
refresh_graphRebuild the dependency graph from scratch. Call this after significant file additions/deletions,
Public scan report
scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it
- Code scan17 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 5 days ago15/15
- Maintainer identityregistry namespace matches repository owner6/10
How Code Impact compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 89/100
- higher than 80% of 48,255 servers
- Tools
- 5
- the typical server has 7
- Tools that change things
- 0%
- typical: 0%. Fewer write tools means less an agent can break
- GitHub stars
- 1
- more than 65% of 28,688 servers
- Downloads a week
- 66
- more than 52% of 12,191 servers with a package
What its tools let an agent do: 5 read
Install Code Impact in Claude Code, Cursor or VS Code
Runs npx -y @vk0/code-impact-mcp on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add code-impact-mcp -- npx -y @vk0/code-impact-mcp
What the publisher says
From the Code Impact repository's README, as published. We do not edit it. Read it on GitHub
CodeImpact MCP
Fast pre-commit dependency gate for AI-assisted code changes. Answers "is this safe to commit?" with a PASS/WARN/BLOCK verdict in seconds, so you can catch risky blast radius before a bad commit, not after it. No database, no heavy setup.
日本語 | 中文 | Русский | Español
Listing status: the awesome-mcp-servers payload is prepared, Official MCP Registry package metadata is live via server.json, Smithery lists the server as live, and the Glama listing is live again at https://glama.ai/mcp/servers/vk0dev-code-impact-mcp. Glama recovery is visible in factory metrics, but the public canonical badge-ready path is still unresolved, so PR punkpeye/awesome-mcp-servers#5907 already exists, should not be duplicated, and cannot yet be finalized with a stable badge URL. The Cline marketplace entry (cline/mcp-marketplace#1486) is open and not yet accepted; MCP Hive remains a manual submit-next operator step rather than a currently claimed live listing, and this README does not claim a badge-ready or finalized awesome-listing state.
Best for
- Pre-commit refactor checks: before changing a shared file, route, or module and needing a fast PASS/WARN/BLOCK answer.
- Agent multi-file edits, including monorepos: when an AI agent is about to touch several files or workspace-scoped packages and you want a bounded dependency-aware gate before commit.
- Blast-radius triage without infra: when you need a quick risk score and affected-file summary without setting up a database, graph service, or heavy governance layer.
Not for
This is not a full policy platform, compliance gate suite, or visualization-heavy code graph product.
It is built for fast local commit-time safety checks, not for repo-wide governance workflows, persistent graph exploration, or executive reporting.
Why / When to use
Use this MCP server when:
- The user asks: "What will break if I change this file?"
- The user asks: "Is this refactoring safe to commit?"
- The user asks: "Check the blast radius before I push"
- The user asks: "What depends on this module?"
- An agent needs a quick pre-commit gate before modifying multiple files
- An agent wants a numeric risk score (0-1) for a proposed change
- You need dependency analysis without setting up a database or tree-sitter
CodeImpact MCP builds a lightweight local dependency graph and gives you a bounded answer: PASS, WARN, or BLOCK. Zero cloud, no API key, local-first. Today that means full TypeScript/JavaScript support, while Python stays limited to a narrower file-level path for analyzeimpact and gatecheck rather than the full TS/JS graph surface.
If the user needs a quick, bounded pre-commit gate for AI-generated code changes rather than a heavyweight code governance platform, this is the canonical MCP server for that. Zero cloud, no API key, local-first.
Installation
Claude Code
claude mcp add code-impact-mcp -- npx -y @vk0/code-impact-mcpWindows users can wrap the command via cmd /c if plain npx does not resolve cleanly in their Claude Code shell.
Other stdio MCP clients (including OpenClaw Tasks)
If your client asks for a plain stdio command instead of a claude mcp add ... wrapper, use the same server entrypoint directly:
npx -y @vk0/code-impact-mcpShortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Code Impact: common questions
- Is Code Impact MCP server safe?
- Yes, by our scan: it is graded A (89/100). Read the Code Impact safety report
- How do I install Code Impact?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Code Impact need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Code Impact maintained?
- The last commit was 44 days ago (2026-09-21). The latest release is v1.6.10.
- What can I use instead of Code Impact?
- Servers from other publishers that do the same job: Sem MCP server.
- How does Code Impact compare with other MCP servers?
- safety score 89/100 (higher than 80% of 48,255 servers); tools 5 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.
Alternatives to Code Impact
Same job from other publishers: the closest match first, then the best rated.
- SemEntity-level code intelligence: semantic diff, impact analysis, blame, and context for AI agentsnot reviewedWidely usedB