Skip to main content
Glama
nikolai-vysotskyi

trace-mcp

by nikolai-vysotskyi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to trace-mcp

No user-submitted related servers found.

    Related Servers

    • LAIN-mcp

      spuentesp
      A
      license
      Not graded
      quality
      A
      maintenance
      A persistent code-intelligence MCP server that builds a queryable knowledge graph of your codebase, enabling AI assistants to perform cross-file structural reasoning, dependency analysis, and blast radius detection.
      6
      MIT

    • LensPR

      kyrylopr
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that builds a dependency graph of your codebase, giving AI agents structural understanding to analyze impact, find context, and make safe modifications across languages and infrastructure.
      MIT

    • Orihime

      srinivasan-sundaresan95
      A
      license
      A
      quality
      C
      maintenance
      Cross-repository code knowledge graph MCP server for Java, Kotlin, JavaScript, and TypeScript. Indexes source code into embedded KuzuDB via tree-sitter and exposes 30+ tools for call-flow tracing, multi-hop taint analysis (OWASP/CWE/PCI/STIG), entry-point reachability filtering, performance hotspot detection, and license compliance — without reading source files. 95% fewer tokens vs source-read
      33
      1
      MIT

    • code-atlas

      lusiem
      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

    • spider-map

      rofid-c
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that analyzes codebases to provide dependency graphs, impact analysis, and file insights across 15+ programming languages, enabling AI assistants to understand project structure and navigate code efficiently.
      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.8/5.0

    Scored across 29 tools

    Disambiguation3/5

    There is meaningful overlap among the code-lookup tools (search, search_text, find_usages, get_feature_context, get_task_context, plan_turn), and among analytics tools (get_session_stats, get_session_analytics, get_optimization_report, get_real_savings, get_usage_trends). The descriptions do include cross-references that help disambiguate, but an agent could still misroute a request between several context-gathering tools.

    Naming Consistency3/5

    The naming follows a mostly understandable convention: get_* for retrievals and verb_noun for mutations/actions. However, it is mixed: search and search_text sit alongside find_usages, plan_turn, batch, and load_tools, so there is no single consistent verb_noun or get_* pattern throughout the set.

    Tool Count2/5

    With 29 tools, the surface is above the 25-tool threshold for 'too many' and spans several distinct subdomains: code intelligence, context retrieval, decision memory, session analytics, and tool management. Each tool may have a purpose, but the set would be easier to navigate if split into focused servers or trimmed.

    Completeness4/5

    The tool surface is broad and covers code lookup, symbol relationships, context assembly, diagnostics, edit reindexing, change impact, decision memory, session analytics, and tool loading. Minor gaps exist, such as not every mentioned helper (e.g., assess_change_risk, add_decision) being a directly exposed tool, but agents can accomplish the core workflows without dead ends.

    Maintenance

    ActivityActive
    ResponsivenessResponsive

    Resources