Skip to main content
Glama
Sign In
Ratatosk

Ratatosk

by basphere
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Remote

Related Servers

Alternatives to Ratatosk

No user-submitted related servers found.

    Related Servers

    • Vigia

      MatiasDelosSantos
      A
      license
      A
      quality
      B
      maintenance
      Verified, 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.
      12
      1
      AGPL 3.0

    • Adaptive Tech Radar MCP

      SerhiiHirus
      A
      license
      A
      quality
      B
      maintenance
      Enables developers to monitor verified upstream releases, sanitize untrusted changelogs, score updates against a local stack profile, and prepare structured verification plans before adopting AI and LLMOps dependencies.
      5
      MIT

    • end-of-life-mcp

      arhancanli
      A
      license
      A
      quality
      B
      maintenance
      Enables 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.
      3
      1
      MIT

    • driftwatch-mcp

      dhughes6071
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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
    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    TDQS

    A4.5/5.0

    Scored across 7 tools

    Disambiguation5/5

    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.

    Naming Consistency4/5

    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.

    Tool Count5/5

    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.

    Completeness5/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessLimited data

    Resources