Skip to main content
Glama
Sign In
vdiff

vdiff

by mcurmi05
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to vdiff

No user-submitted related servers found.

    Related Servers

    • lurq

      jadenryu
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding agents to verify, compare, and safely upgrade npm packages by scoring packages from public signals and sandboxed co-installation, detecting breaking API surface changes, and rewriting code that upgrades break.
      86 npm
      8
      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

    • ts-docs-mcp

      xvantz
      A
      license
      A
      quality
      D
      maintenance
      An MCP server that gives AI coding agents accurate, version-aware API documentation for any npm package — straight from the source.
      1
      34 npm
      MIT

    • dev.augments/mcp

      beatricen1965
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP clients to fetch context-aware API signatures, prose documentation, and code examples for any npm package, along with version diffs, migration guides, error diagnosis, package comparison, and dependency scanning.
      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.1/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have distinct purposes: one resolves package versions, the other computes breaking changes. There is no ambiguity or overlap.

    Naming Consistency5/5

    Both tools follow a consistent verb_noun pattern with snake_case (resolve_package, get_breaking_changes), making them predictable.

    Tool Count4/5

    With only two tools, the server is minimal but well-suited to its niche purpose of version analysis. It could benefit from additional utilities like listing versions, but the count is not inappropriate.

    Completeness4/5

    The tools cover the essential workflow: resolve a package name to a version, then get breaking changes. While there are no additional features like changelog retrieval or multi-package comparison, the core functionality is complete.

    Maintenance

    ActivityInactive
    ResponsivenessSyncing

    Resources