Ratatosk
Related Servers
Alternatives to Ratatosk
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityNot gradedmaintenanceVerified, dated facts for AI coding agents: what breaks between npm package versions (diffed from TypeScript types), per-version vulnerabilities, the newest version compatible with a given Node/Python/Rust/PHP, end-of-life dates of ~480 runtimes and frameworks, and AI model prices. Covers npm, PyPI, crates.io and Packagist.AGPL 3.0
- AlicenseAqualityBmaintenanceEnables checking project files like Dockerfile, .nvmrc, and CI workflows to determine whether pinned runtime, database, and OS versions are still supported, providing end-of-life dates, latest patches, and upgrade targets for 470+ products.31MIT
- AlicenseNot gradedqualityBmaintenanceEnables querying the CNCF landscape to search for projects, get detailed information, GitHub metrics, maturity status, and case studies for technology decision support.4Apache 2.0
- 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
- AlicenseNot gradedqualityAmaintenanceEnables 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

Modelmeterofficial
AlicenseNot gradedqualityCmaintenanceEnables AI agents to query model pricing, deprecations, and cost estimates via a machine-readable changelog of the AI stack.1MIT
TDQS
Scored across 7 tools
Each tool has a distinct role: project discovery, release summaries, release detail, change feed, matter expansion, entity reverse lookup, and running-stack comparison. The descriptions explicitly call out when not to use a particular tool, which removes most ambiguity.
Six of seven tools follow a clear verb_noun pattern: get_release, get_matter, list_releases, list_changes, list_projects, check_stack. The exception is changes_by_entity, which is a noun phrase rather than a verb-led name, but all names are still lowercase snake_case and otherwise predictable.
Seven tools is a well-scoped size for this domain. Each tool covers a distinct part of the release-change and upgrade-analysis workflow, and none feels redundant or superfluous.
The toolset covers the full workflow: discovering tracked projects, listing releases, reading release details, syncing change feeds, expanding matters across releases, doing entity-based reverse lookup, and checking a running stack against known changes. Drill-down paths are explicit and there are no obvious dead ends.