Skip to main content
Glama
MShekow

package-version-check-mcp

by MShekow
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to package-version-check-mcp

No user-submitted related servers found.

    Related Servers

    • agent-versions

      AndrewTtofi
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding agents to fetch the real latest versions of packages from npm, PyPI, crates.io and the Go module proxy, then check manifests or whole projects for outdated dependencies and rewrite them in place. It also reports the current releases and underlying dependency stacks of AI coding tools like Claude Code, Codex and Gemini CLI.
      1
      MIT
    • packagetrackdev-mcp by packagetrack-dev

      packagetrackdev-mcpofficial

      packagetrack-dev
      A
      license
      A
      quality
      C
      maintenance
      Enables coding agents to query package release histories, version lists, and change summaries across PyPI, npm, crates.io, Packagist, NuGet, pub.dev, Go, and Maven Central to inform dependency upgrades and detect withdrawn versions.
      5
      MIT

    • package-intel-mcp

      datakoot
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides software supply-chain intelligence for AI agents, enabling them to query package metadata, versions, downloads, dependencies, and health signals for npm, PyPI, and crates.io packages without API keys.
      MIT

    • container-tag-finder

      tldev
      F
      license
      A
      quality
      D
      maintenance
      Enables AI agents to retrieve the latest semantic version tags for container images from Docker Hub, GHCR, Quay, and other OCI registries, allowing them to pin specific versions for reproducible deployments.
      5
      -
    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

    A4.2/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool targets a distinct domain (GitHub Actions, ecosystem packages, dev tools, tool listing). Descriptions clearly differentiate between packages and tools, reducing ambiguity.

    Naming Consistency5/5

    All tools follow a consistent 'get_<specific_noun>' snake_case pattern, making it easy to predict and understand tool purposes.

    Tool Count5/5

    Four tools is appropriate for a focused version-checking service—neither too few nor too many, covering the essential operations.

    Completeness5/5

    The tool surface covers the major version-checking needs: GitHub Actions, package ecosystems, dev tools, and a way to list supported tools. No obvious gaps for the stated purpose.

    Maintenance

    ActivityActive
    ResponsivenessResponsive

    Resources