Skip to main content
Glama
ip2k

rarefaction

by ip2k
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to rarefaction

No user-submitted related servers found.

    Related Servers

    • CodeCortX-MCP

      kensave
      F
      license
      Not graded
      quality
      D
      maintenance
      A lightning-fast, language-agnostic code analysis MCP (Model Context Protocol) server built in Rust
      9
      -

    • corbel

      BETAER-08
      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

    • code-analyze-mcp

      clouatre-labs
      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.
      6
      Apache 2.0

    • genpark-agent-codebase-ast

      Alpha-Park
      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
      -
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A4.3/5.0

    Scored across 2 tools

    Disambiguation5/5

    orient performs the actual context retrieval while status is a diagnostic/setup check for profiles and freshness. The two purposes are clearly distinct with no overlap, and the descriptions explicitly state the call order (status before orient).

    Naming Consistency4/5

    Both names are single lowercase tokens in a consistent style, but one is a verb (orient) and the other a noun (status), so there is no single predictable verb_noun convention. Still readable and non-chaotic.

    Tool Count3/5

    Only two tools for a code-orientation/LSP-indexing domain feels thin; the surface is tightly scoped but leaves little room for related operations. It borders on under-provisioned for the apparent scope.

    Completeness3/5

    The pair covers orientation and environment checking, which are the core workflow, but there is no way to refresh/rebuild indexes, enumerate indexed projects, or query symbols separately. Notable gaps exist that an agent may hit in larger workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources