DepTime
Related Servers
Alternatives to DepTime
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceProvides 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.9MIT
- AlicenseAqualityCmaintenanceEnables 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.332 npmMIT

Errata MCP Serverofficial
AlicenseAqualityFmaintenanceEnables 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.3423 npmMIT- AlicenseNot gradedqualityAmaintenanceEnables AI coding agents to query a local structural code graph for focused context, inspect relationships and impact, and carry recorded mistakes into later sessions.24 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables 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 PyPI10MIT
- AlicenseBqualityDmaintenanceEnables AI agents to index local Python repositories and retrieve code intelligence through semantic search, caller lookups, hybrid context expansion, and visualization.5MIT
TDQS
Scored across 6 tools
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.
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.
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.
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.