Skip to main content
Glama

Related Servers

Alternatives to rarefaction

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Local MCP server that gives your coding agent a code graph of your repository: who calls a function, what a change reaches, which tests cover it.
      1,126
      Apache 2.0
    • F
      license
      Not graded
      quality
      D
      maintenance
      A lightning-fast, language-agnostic code analysis MCP (Model Context Protocol) server built in Rust
      9
      -
    • A
      license
      A
      quality
      A
      maintenance
      Call graph MCP server for Rust, Python, TypeScript, TSX, and JavaScript. Every caller and callee carries a resolution field showing how the reference was matched to a definition, plus multi-hop impact analysis for refactoring. Local-only, single binary, no network egress. Benchmarked against grep, ripgrep, and ctags on a 120-item hand-verified golden set, including the cases where it loses.
      3
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Standalone MCP server for code structure analysis using tree-sitter. Directory trees, symbol definitions, and call graphs without reading raw source files. Supports Rust, Python, Go, Java, TypeScript, Fortran, JavaScript, C/C++, and C#. Benchmarked up to 68% fewer tokens vs native tools.
      7
      Apache 2.0
    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables coding agents and MCP-compatible clients to parse multi-file AST dependency graphs and extract minimum context through symbol call-tree slicing. It provides deterministic, zero-dependency execution over JSON-RPC stdio.
      7
      -

    TDQS

    A3.9/5.0

    Scored across 3 tools

    Disambiguation4/5

    The three tools have distinct roles: status is a preflight check, orient retrieves symbol context, and scope predicts change impact. There is minor overlap in that status and orient both reference profiles, but the descriptions clearly separate their purposes.

    Naming Consistency3/5

    All names are single lowercase words with no underscores or camelCase, which is visually consistent. However, they mix grammatical roles (status is a noun, orient is a verb, scope is ambiguous), so there is no predictable verb_noun pattern.

    Tool Count4/5

    Three tools is a tight, focused set for a code-orientation server, and each tool serves a clear step in the workflow. The count is slightly minimal but reasonable given the narrow scope.

    Completeness3/5

    The surface covers preflight, context retrieval, and impact analysis, but lacks any symbol search or discovery operation—users must already know a path:line:column. This is a notable gap for a code intelligence tool, though core workflows are partially supported.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues