stalemap
Related Servers
Alternatives to stalemap
No user-submitted related servers found.
Related Servers
- 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.52 PyPI10MIT
- AlicenseNot gradedqualityCmaintenanceEnables coding agents to retrieve maintainer-written release notes and compare installed versus target dependency versions, search packages, and report on projects pushed to a dashboard.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to fetch the real latest versions of packages from npm, PyPI, crates.io and the Go module proxy, then check manifests or whole projects for outdated dependencies and rewrite them in place. It also reports the current releases and underlying dependency stacks of AI coding tools like Claude Code, Codex and Gemini CLI.1MIT
- AlicenseAqualityDmaintenanceProvides accurate, source-grounded breaking-change briefings for npm packages by reading real GitHub release notes and CHANGELOGs, helping coding agents avoid hallucinated dependency migrations.38 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to persist and retrieve durable project knowledge across coding sessions, capturing decisions, conventions, lessons and reusable skills through ordinary chat requests. It supports searching, editing and reviewing saved items, and promoting local notes into Git-shareable versioned knowledge alongside repository changes.53 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to identify exactly what broke between two dependency versions, with citations for every claim, and to verify package existence to catch typosquatting, all without requiring an API key.MIT
TDQS
Scored across 4 tools
search_changes, package_changes, and project_changes all report dependency API changes, which creates some overlap, but each has a distinct entry point (free-text topic, specific npm package, whole-project scan) and the descriptions give clear trigger conditions. The boundaries are mostly learnable, with only mild risk of picking the wrong one.
Three tools share the strong '_changes' family pattern (search/package/project_changes), and check_notes is a readable verb_noun name. The first word shifts between verb and noun, a minor inconsistency, but overall the convention is predictable.
Four tools is well-scoped for a focused domain (surfacing post-cutoff dependency changes). Each tool earns its place and none feels redundant or padded.
The surface covers the key entry points: topic search, package-specific lookup, project scan, and notes staleness check. The notable gap is that check_notes only reads staleness with no tool to create or refresh the notes block, though that may be handled elsewhere.