Skip to main content
Glama
dongju93

dependency-compat-mcp

by dongju93

Related Servers

Alternatives to dependency-compat-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      D
      maintenance
      A comprehensive MCP server for checking package versions and rating package quality across Python (PyPI), JavaScript/TypeScript (npm), Dart (pub.dev), and Rust (crates.io) ecosystems.
      5
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      An MCP server that provides cross-validated npm dependency fitness verdicts, including deprecation, malicious detection, and safe migration target inference.
      2
      30 npm
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      MCP server for checking packages against an AI-aware vulnerability database, including CVEs, slopsquatting, CISA KEV, and MCP-server trust profiles.
      10
      Elastic 2.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that checks npm and PyPI package health, providing maintenance signals, version info, CVE counts, and alternative suggestions.
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      An MCP server that queries 19 package registries (npm, PyPI, crates.io, etc.) to retrieve the latest version of packages and their metadata.
      21
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that acts as a temporal verification firewall, checking structured assumptions or diffs against immutable version receipts to return allow/block/abstain with cited evidence.
      MIT

    TDQS

    A4.4/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: check_compatibility compares two exact releases, while get_compatibility_context retrieves declarations for a single release. There is no overlap in functionality, and the verbose descriptions reinforce the boundaries.

    Naming Consistency5/5

    Both tool names follow the consistent verb_noun pattern (check_compatibility, get_compatibility_context). The naming style is uniform and predictable.

    Tool Count3/5

    With only 2 tools, the server is on the low end of the typical range. The narrow focus on compatibility checking makes this borderline, but it feels slightly thin for a general-purpose dependency tool.

    Completeness4/5

    The core domain operations are covered: checking compatibility between two releases and retrieving compatibility context for one release. Minor gaps exist, such as no tool to list available versions or resolve ranges, but these are explicitly out of scope and agents can work around them.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues