Skip to main content
Glama
pdogra1299

Dependency Tracer MCP Server

by pdogra1299
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Dependency Tracer MCP Server

No user-submitted related servers found.

    Related Servers

    • N3MO

      RajX-dev
      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
      -

    • Weavatrix

      Weavatrix
      A
      license
      Not graded
      quality
      A
      maintenance
      Provides a dependency graph of any local repository with tools for change impact, transitive dependents, health audits, and more, enabling AI coding agents to see structure and refactor safely.
      4,912 npm
      4
      MIT

    • codelattice

      aiulms
      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
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.9/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool has a distinct purpose: listing symbols, getting detailed info, tracing callers/callees, searching, impact analysis, indexing, and status. No ambiguity between them.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern (e.g., get_module_symbols, trace_callees, index_codebase). The naming is clear and predictable.

    Tool Count5/5

    With 10 tools, the set covers the core functionality of dependency tracing without being bloated. Each tool seems necessary and well-scoped.

    Completeness4/5

    The tools cover indexing, symbol lookup, dependency tracing in both directions, impact analysis, and test context generation. Minor gap: no explicit tool to list all modules or files, but search_symbols and get_module_symbols partially cover it.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources