Skip to main content
Glama

Related Servers

Alternatives to library-enrichment

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables agents to search pinned robotics code and reusable task findings across frameworks, inspect provenance and requirements, and prepare supported upstream sources via recipes without executing robot code.
      Apache 2.0
    • A
      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.
      MIT
    • 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.
      50 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.
      258 PyPI
      4
      MIT
    • A
      license
      Not graded
      quality
      D
      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.
      112 npm
      MIT

    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

    ActivitySlowing
    ResponsivenessNo issues