Skip to main content
Glama
Sign In
Breakage Calendar MCP server

Breakage Calendar MCP server

by CyberNative-AI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Related Servers

Alternatives to Breakage Calendar MCP server

No user-submitted related servers found.

    Related Servers

    • since-cutoff

      MohammadHijjawi97
      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

    • traplens

      CloudCorpRecords
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables coding agents to look up dated, verified API breakages by provider or by matching error text, each with symptoms, cause, fix, and a code example. Agents can also file new traps after fixing a failure and confirm whether known traps still hold, with all calls forwarded to the upstream registry.
      295 npm
      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

    • 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
    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.1/5.0

    Scored across 5 tools

    Disambiguation4/5

    The three check_* tools are separated primarily by input source: a list of dependency identifiers, raw file contents, or a local folder path. The descriptions make this boundary reasonably explicit, though an agent with a repository in hand could plausibly hesitate between check_files and check_repository. list_upcoming_breaks vs get_break are cleanly distinct (browse vs fetch by id).

    Naming Consistency5/5

    Every name is snake_case verb_noun (check_dependencies, check_files, check_repository, list_upcoming_breaks, get_break) with a single consistent verb family per action type. No mixed conventions or case styles.

    Tool Count5/5

    Five tools is well scoped for a breakage-calendar lookup service: three input-variant checkers plus browse and detail retrieval. Each tool earns its place and nothing looks redundant padding.

    Completeness4/5

    The surface covers discovery (list), detail (get), and checking across all plausible input forms (dependency list, raw files, local repo). Minor gaps remain: no date-range or past-break filtering on the list tool, and no way to look up breaks by affected dependency name short of free-text filtering.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources