Skip to main content
Glama
packagetrack-dev

packagetrackdev-mcp

Official
by packagetrack-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to packagetrackdev-mcp

No user-submitted related servers found.

    Related Servers

    • package-version-check-mcp

      MShekow
      A
      license
      A
      quality
      A
      maintenance
      Enables AI coding agents to retrieve the latest stable versions of packages and tools across multiple ecosystems, preventing outdated dependency versions in generated code.
      4
      216 PyPI
      8
      Apache 2.0

    • package-registry-mcp

      mikeysrecipes
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to search and retrieve detailed package information from multiple package registries (NPM, crates.io, NuGet, PyPI, Go).
      1,047 npm
      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

    • driftwatch-mcp

      dhughes6071
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding agents to identify exactly what broke between two dependency versions, with citations for every claim, and to verify package existence to catch typosquatting, all without requiring an API key.
      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.8/5.0

    Scored across 5 tools

    Disambiguation4/5

    Each tool maps to a distinct step in the workflow: searching, inspecting versions, reading release changes, listing projects, and generating a project report. package_changes and package_versions share the same prefix and both relate to versions, so they could be confused at first glance, but the descriptions clearly separate change notes from version metadata.

    Naming Consistency3/5

    The names are uniformly snake_case and readable, but the naming pattern is mixed: search_packages and list_projects follow verb_noun, while package_changes, package_versions, and project_report are noun phrases. A consistent verb_noun style such as list_package_changes and get_project_report would improve predictability.

    Tool Count5/5

    Five tools is well within the ideal scope for a focused server, and each tool earns its place in the dependency-tracking and upgrade workflow. Nothing feels redundant or tacked on.

    Completeness5/5

    The toolset covers a complete workflow: find packages, inspect version status, read release notes, list the user's projects, and pull an upgrade-oriented project report. There are no obvious dead ends for the server's apparent purpose of supporting dependency review and upgrades.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources