Skip to main content
Glama

Related Servers

Alternatives to library-enrichment

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      Provides up-to-date, version-specific documentation and code examples for software libraries directly to LLMs, enabling resolution of library identifiers and retrieval of relevant documentation with code snippets.
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Provides read-only, provenance-first repository navigation for agents and humans, with ranked lexical retrieval, exact query, document handles, symbol context, and change impact analysis.
      49 npm
      Apache 2.0
    • 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.
      3
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that enables coding agents to safely verify npm/PyPI packages, retrieve cited briefs, discover GitHub repos, and fetch canonical docs, with fail-closed OSV vulnerability checks and injection-hardened output.
      143 npm
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Enables coding agents to analyze a repository evidence-first, answering questions as verifiable claims with source evidence, targeted test observations, and reference resolution.
      5
      3
      Apache 2.0

    TDQS

    B3.4/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool maps to a distinct phase in the research workflow: status, identity, overview, evidence search, symbol inspection, release comparison, usage verification, artifact retrieval, and job control. Even the two preflight tools are clearly separated by readiness vs. identity.

    Naming Consistency3/5

    The majority use verb_noun (search_evidence, inspect_symbol, compare_releases, verify_usage, read_artifact), but service_status, library_overview, and job_control are noun_noun, creating an inconsistent pattern. Names remain readable, so not chaotic.

    Tool Count5/5

    Nine tools is a well-scoped count for a specialized library-research server; each tool covers a distinct step without redundancy or bloat.

    Completeness4/5

    The set covers the full discovery, inspection, comparison, verification, and retrieval lifecycle, with job control for long operations. The only minor gap is the absence of an explicit write-back/enrichment-submission tool, though the server appears read-oriented by design.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues