Skip to main content
Glama

Related Servers

Alternatives to wheelripe

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      maven-mcp gives AI agents (Claude Code, Cursor, Codex, Grok Build and any MCP client) live knowledge about JVM dependencies. It looks up the latest versions on Maven Central, finds outdated dependencies in Maven, Gradle and version catalog files, checks known vulnerabilities via OSV.dev, pulls changelogs and licenses, and builds dependency graphs with deps.dev. It's a single-file Python 3.9+ serve
      21
      37
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that watches upstream API providers for breaking changes, scans your codebase for impact, and drafts migration fixes locally, all offline-first with zero network.
      99 npm
      1
      AGPL 3.0
    • A
      license
      A
      quality
      B
      maintenance
      An MCP server that scans your lockfiles (npm, PyPI, Go, Rust, Ruby, PHP) for known vulnerabilities, enriches with EPSS exploit probability scores, and recommends fix versions. $14/mo — not per-seat.
      9
      1
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      9 MCP servers for React + TypeScript development automation — component scaffolding, dependency auditing, WCAG accessibility checking, test generation, TypeScript enforcement, and monorepo management. 134 tests, CI on Node 20+22.
      7
      96 npm
      3
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      deptrust is a CLI that checks package versions for known vulnerabilities across npm, PyPI, crates.io, Go modules, RubyGems, NuGet, Maven, Packagist, pub.dev, CocoaPods, Hex.pm, Hackage, GitHub Actions, and more. It runs locally as a CLI and as an MCP server. It calls public package registry and OSV APIs directly; there is no hosted deptrust service to trust or configure.
      95 npm
      61
      MIT

    TDQS

    A4.1/5.0

    Scored across 2 tools

    Disambiguation5/5

    check_python_upgrade audits an entire project's dependencies for wheel availability on a target Python/platform, while explain_wheel decodes a single wheel filename using tag rules. Their inputs and outputs are clearly different, so an agent can choose correctly; the overlap is only domain-level, not functional.

    Naming Consistency5/5

    Both names are snake_case and start with a verb (check_..., explain_...), followed by the object or context. The patterns are predictable and consistent across the tool set.

    Tool Count4/5

    Two tools is slightly below the typical 3–15 range, but this is a narrow wheel-compatibility utility where the pair covers both batch project analysis and single-artifact explanation. There is no redundant tool, so the small surface is reasonable rather than deficient.

    Completeness4/5

    The tools cover batch dependency upgrade readiness, status classification, upstream tracking, and single-wheel tag explanation. A minor gap is the lack of a standalone package/release wheel-matrix lookup, but the core upgrade decisions are supported.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data