Skip to main content
Glama
Anicodeth

breaking-changes-mcp

by Anicodeth
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to breaking-changes-mcp

No user-submitted related servers found.

    Related Servers

    • dependency-migration-mcp

      SolvoHQ
      F
      license
      Not graded
      quality
      C
      maintenance
      Provides structured migration briefs for LLM coding agents covering breaking changes, codemod coverage, and hallucination warnings for major version bumps of packages like tailwindcss, next, and react.
      -

    • 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

    • vdiff

      mcurmi05
      F
      license
      A
      quality
      A
      maintenance
      Breaking-change diffs for npm packages, served over REST and MCP, so coding agents stop writing code against outdated API knowledge.
      2
      -

    • upgrade-pilot-mcp

      kdinisv
      A
      license
      B
      quality
      D
      maintenance
      Enables AI agents to safely upgrade JavaScript and TypeScript projects through dependency analysis, upgrade path detection, breaking change identification, codemod application, and PR summary generation.
      14
      4
      MIT

    • pkgtruth

      hxckya
      A
      license
      A
      quality
      A
      maintenance
      Enables AI coding agents and CI to vet npm dependencies before they reach the lockfile, flagging hallucinated, slopsquatted, or otherwise risky packages with evidence-backed verdicts.
      3
      493
      3
      MIT
    Deploy Server
    RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

    TDQS

    A4.4/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: listing versions, fetching breaking changes, and fetching full changelog. The overlap between breaking_changes_between and changelog_between is well-defined, with descriptions explicitly stating breaking-only vs full release notes, so agents should not confuse them.

    Naming Consistency4/5

    All names use snake_case and are descriptive, but there is a minor mix: list_versions follows verb_noun while the other two follow noun_preposition. The '_between' suffix is consistent for the pair, making the set predictable overall.

    Tool Count5/5

    Three tools is well-scoped for the narrow domain of npm package release notes. Each tool earns its place, covering the essential workflow of discovering versions and retrieving release notes/breaking changes without redundancy.

    Completeness4/5

    The set covers the core lifecycle for the stated purpose: version discovery, breaking changes, and full changelog. A minor gap is that there is no direct way to get a single version's notes without specifying a 'from' version, but this can be worked around using list_versions and the between tools.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources