Skip to main content
Glama

Related Servers

Alternatives to DepTime

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Provides a local, version-exact API index for installed Python and TypeScript packages, enabling accurate lookups and static code checking that catches hallucinated or misused APIs without executing the code.
      9
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI coding agents to inspect project dependency versions, resolve version constraints, and audit Python code for deprecated or incompatible APIs using authoritative evidence and local AST analysis.
      3
      32 npm
      MIT
    • A
      license
      A
      quality
      F
      maintenance
      Enables AI coding agents to check PyPI and npm packages for sandbox-verified outdated-code corrections, search errors by text or traceback, and submit confirmation or dispute reports.
      3
      423 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables coding agents to query breaking API changes in dependencies since a model's training cutoff, retrieve project dependency change summaries, and look up model training cutoff dates.
      35 PyPI
      10
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      Enables AI agents to index local Python repositories and retrieve code intelligence through semantic search, caller lookups, hybrid context expansion, and visualization.
      5
      MIT

    TDQS

    A4.3/5.0

    Scored across 6 tools

    Disambiguation4/5

    Most tools have clearly distinct roles: coverage checks indexed packages, explain_error handles runtime exceptions, and check_upgrade validates code against a target version. There is some overlap between check_upgrade and diff_versions, and between check_symbols and symbol_history, but the descriptions explicitly cross-reference each other to guide selection.

    Naming Consistency3/5

    The names mix conventions: two use check_ + noun, two use verb_noun, one is a bare noun (coverage), and one is noun_noun (symbol_history). The names are still readable and domain-specific, but there is no predictable pattern across the set.

    Tool Count5/5

    Six tools is well-scoped for a dependency and API compatibility checking server. Each tool covers a distinct query type (coverage, upgrade breaks, symbol checks, version diffs, runtime errors, symbol history) without obvious redundancy.

    Completeness5/5

    The surface covers the full workflow: checking package coverage, preflighting symbols, comparing versions, validating code during upgrades, explaining runtime import/attribute/type errors, and inspecting symbol history. No obvious lifecycle gap remains for the stated dependency compatibility domain.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues