Skip to main content
Glama
vk0dev

Code Impact MCP

by vk0dev

Related Servers

Alternatives to Code Impact MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      AI-powered codebase intelligence tool that builds a dependency graph of a git repo for structural Q&A and pre-PR code review. It exposes MCP tools for blast radius, review sessions, and static analysis, running locally over stdio with no LLM or network dependencies.
      MIT
    • F
      license
      A
      quality
      A
      maintenance
      Deterministic code intelligence engine — indexes 27 languages into a queryable symbol graph for real-time blast-radius analysis, no embeddings or LLM calls.
      5
      25
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Local code-graph engine for AI coding workflows: static analysis of Rust, Cangjie, ArkTS, TypeScript/JavaScript, C/C++, Python, and Shell projects into symbols, imports, call graphs, and quality gates, with pre-commit change review and impact analysis. Read-only by design — never executes build scripts or uploads code.
      6
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Local-first security check for AI coding agents — finds hardcoded secrets, exposed .env files, git-history leaks and vulnerable dependencies (OSV), entirely on your machine. Ask your agent "is this safe to ship?" and get a Launch Readiness score with a fix for every finding.
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      AI-powered dependency vulnerability and breaking change analyzer that scans dependencies, identifies vulnerabilities via OSV.dev, and uses AI to assess real impact and suggest fixes.
      3
      Apache 2.0

    TDQS

    A4.2/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: get_dependencies shows direct relationships, analyze_impact computes transitive blast radius, detect_cycles finds circular dependencies, gate_check provides a safety verdict, and refresh_graph rebuilds the graph. No overlap or ambiguity.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (get_dependencies, analyze_impact, detect_cycles, gate_check, refresh_graph), making them predictable and easy to distinguish.

    Tool Count5/5

    With 5 tools, the server is well-scoped for its purpose of dependency impact analysis. Each tool covers a necessary aspect, and there are no superfluous or missing tools for the core workflow.

    Completeness5/5

    The tool set covers the full lifecycle: graph building (refresh_graph), dependency inspection (get_dependencies), impact prediction (analyze_impact), cycle detection (detect_cycles), and pre-commit validation (gate_check). No obvious gaps for the intended use case.

    Maintenance

    ActivityActive
    ResponsivenessNo issues