Skip to main content
Glama

Related Servers

Alternatives to javats-impact-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      Local-first MCP server that scans a repository once and answers architecture questions from an evidence-backed graph, enabling dependency analysis, impact analysis, and codebase exploration without re-reading the source tree.
      3
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Multi-language code intelligence MCP server providing structured code analysis including symbol search, references, hierarchies, and change impact. Supports 25 languages with persistent indexing and LSP integration.
      45 npm
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      MCP server for persistent code exploration and diff-aware review, exposing explore and review tools to map call paths, blast radius, and generate explainable risk-scored reports.
      13 npm
      2
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      MCP server that exposes code tracing capabilities including journey flows, HTTP seams, and findings from indexed projects, allowing AI assistants to query software architecture.
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      High-performance MCP server for OpenAPI specifications that parses specs, diffs versions, tracks dependencies, and generates code (TypeScript, Rust, Python).
      6 npm
      2
      MIT

    TDQS

    B3.1/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool targets a distinct aspect: indexing, symbol lookup, reference finding, endpoint details, cross-stack impact, git context, and summary aggregation. No overlap in purpose.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern in snake_case (e.g., find_symbol, get_endpoint), making them predictable and easy to differentiate.

    Tool Count5/5

    With 7 tools, the set is well-scoped for a code impact analysis domain. Each tool serves a clear role without being too many or too few.

    Completeness4/5

    The tools cover core workflows: indexing, searching, referencing, endpoint mapping, impact analysis, and git context. Minor gaps exist like direct file content retrieval, but the set is sufficient for its stated purpose.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues