Skip to main content
Glama

Related Servers

Alternatives to Verinoda

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding agents to interrogate a local repository deterministically for symbols, dependencies, call paths, routes, tests, and Git impact, returning verified structured evidence with exact line citations instead of requiring the whole codebase to be read.
      737 PyPI
      3
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Provides local-first repository architecture analysis with file-level proof, enabling agents to map codebases, locate implementations, trace call paths, and assess change impact with deterministic evidence.
      4 npm
      2
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Local-first evidence-backed repository memory for coding agents, providing read-only tools to list concepts, explain them, get governed context packs, and verify claims against the codebase.
      45 PyPI
      11
      Apache 2.0
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding agents to query repository structure, symbols, dependencies, Git history, architecture, memory, impact, and guarded edits through a stable MCP interface, returning ranked task-specific evidence within a context budget.
      6
      Apache 2.0
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables locating evidence for repository questions using CodeGraph or ripgrep, providing verified results and follow-ups.
      14 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables coding agents to query a local, versioned knowledge graph of a software project, retrieving overviews, context packs, evidence, and explanations to make informed changes.
      MIT

    TDQS

    A3.6/5.0

    Scored across 5 tools

    Disambiguation3/5

    project_query and analyze both answer code questions, with project_query focused on ranked locations and analyze on claims/evidence, but the boundary is not always clear. The run_tool meta-tool bundles many sub-operations that overlap with top-level tools, increasing misselection risk. Descriptions help somewhat but overlap remains.

    Naming Consistency3/5

    Names use snake_case consistently, but the word order and verb style are mixed: index_update and run_tool are verb_noun, project_query and code_check are noun_verb/noun phrases, and analyze is a bare verb. This is readable but not a predictable pattern.

    Tool Count5/5

    Five top-level tools is well within the typical 3-15 range and each covers a distinct core workflow: indexing, querying, analysis, checking, and extended operations. The meta-tool run_tool keeps the surface scoped while still exposing many capabilities.

    Completeness4/5

    The set covers indexing, code location search, evidence-based analysis, code existence checking, and a broad set of secondary operations via run_tool. Minor gaps exist in top-level access to symbol-level inspection and project overview, but these are reachable through run_tool.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive