Skip to main content
Glama
tanvi0102

change-impact-assistant

by tanvi0102
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to change-impact-assistant

No user-submitted related servers found.

    Related Servers

    • Scrooge

      De-Cri
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides AI coding agents with pre-edit situational awareness by combining structural call graphs and co-change history to prevent incomplete edits. It surfaces files that historically change together, reducing missed coupled modules.
      3
      MIT

    • mcp-git-chronicle

      luckdevx
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides AI coding agents with Git repository history analysis, including churn hotspot detection, semantic file coupling, and recent context summaries through MCP tools.
      MIT

    • codecanvas-mcp

      donggyun112
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides local static-analysis tools for Python that let coding agents trace call paths, branch guards, side effects, and change impact, producing citation-ready answers with explicit uncertainty signals.
      2
      MIT

    • cms mcp

      mrt150683-lgtm
      A
      license
      Not graded
      quality
      B
      maintenance
      Exposes codebase memory as native tools for AI agents, enabling queries, feature tracing, impact analysis, and alignment verification.
      4
      AGPL 3.0
    Deploy Server
    RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

    TDQS

    A3.6/5.0

    Scored across 5 tools

    Disambiguation4/5

    Most tools are clearly separated by their evidence source or scope: whole-diff analysis vs single-file explanation vs static vs historical. analyze_current_change and explain_affected_file are related but distinct enough in descriptions (whole set vs one file). Some minor overlap remains around which tool to pick for single-file impact evidence.

    Naming Consistency4/5

    Four tools use the get_* prefix and analyze_current_change/explain_affected_file use action_noun. The naming is clear and predictable, though there's a slight mix of get_ vs analyze_/explain_ verbs rather than a single uniform convention.

    Tool Count5/5

    Five tools tightly cover the change-impact domain: list changed files, analyze the whole diff, explain a single file, and query static or historical evidence. No redundancy and no bloat.

    Completeness4/5

    The main workflow is covered: list changed files, run a diff-based impact analysis, and drill into static or historical evidence per file. A possible minor gap is a way to combine static and historical evidence on demand outside the current-diff analysis.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources