Skip to main content
Glama
trianglegrrl

versionator-mcp

by trianglegrrl
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to versionator-mcp

No user-submitted related servers found.

    Related Servers

    • MCP Package Hero

      moinsen-dev
      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

    • freshdeps-mcp

      SolvoHQ
      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

    • pkg-oracle

      julian-martin89
      A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that verifies npm and PyPI packages before installation, checking for existence, known vulnerabilities, OpenSSF scorecard, and typosquatting, returning an ALLOW/WARN/BLOCK verdict.
      MIT

    • Dependency MCP Server

      niradler
      A
      license
      A
      quality
      D
      maintenance
      A Model Context Protocol server for checking package versions and metadata across multiple package managers including npm, PyPI, Maven, NuGet, RubyGems, Crates.io, and Go modules.
      6
      26 npm
      1
      MIT

    • @registry/mcp

      broisnischal
      A
      license
      Not graded
      quality
      D
      maintenance
      Unified MCP server for searching, analyzing, and managing packages across npm, JSR, Deno, and multiple CDN providers with auto-detection.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 21 tools

    Disambiguation5/5

    Each tool targets a distinct package registry or ecosystem, with clear descriptions specifying the exact source (e.g., npm, PyPI, CRAN). There is no ambiguity or overlap between tools.

    Naming Consistency5/5

    All tools follow a consistent 'get_<ecosystem>_<type>' pattern in snake_case (e.g., get_npm_package, get_ruby_gem, get_docker_image). The health_check tool is the only deviation but still fits the overall verb_noun style.

    Tool Count4/5

    With 21 tools, the server covers a broad range of package registries, which is appropriate for a version-checking service. While slightly high, each tool serves a distinct purpose, justifying the count.

    Completeness4/5

    The server covers most major package registries (npm, PyPI, RubyGems, CRAN, etc.) and includes specialized ones like Bioconda and nf-core. The inclusion of a health_check tool is a minor deviation from the core version-checking purpose, but overall the surface is comprehensive.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources