Skip to main content
Glama
packagerating

packagerating MCP Server

Official
by packagerating
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to packagerating MCP Server

No user-submitted related servers found.

    Related Servers

    • pkg-intel-mcp

      JanMaa
      F
      license
      A
      quality
      D
      maintenance
      Package intelligence for AI coding agents that checks npm and PyPI package health, deprecation, vulnerabilities, bundle size, and compares alternatives.
      5
      -

    • Dependency Health MCP

      ux-xd
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables checking whether software packages are deprecated, archived, stale, active, or unknown with supporting evidence, auditing dependency manifests, and looking up runtime support and end-of-life dates.
      MIT
    • Fetter MCP by fetter-io

      Fetter MCPofficial

      fetter-io
      F
      license
      Not graded
      quality
      D
      maintenance
      Provides real-time Python package vulnerability data, enabling AI agents to check CVEs, CVSS scores, and safe versions for informed dependency decisions.
      1
      -

    • package-truth

      arhancanli
      A
      license
      A
      quality
      B
      maintenance
      Enables checking packages across npm, PyPI, Go, Maven, Cargo, NuGet, and RubyGems for existence, deprecation, known vulnerabilities, and license issues before installation, providing verdicts like does_not_exist, risky, verify, or ok.
      3
      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

    A4.4/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a distinct purpose: listing scored packages, fetching a single package's score, and enqueueing crawls without waiting. Although get_package can trigger a crawl, the key difference is that request_crawl is for background pre-warming, so there is no ambiguity.

    Naming Consistency5/5

    All tool names follow the same verb_noun pattern: list_packages, get_package, request_crawl. The naming is predictable and consistently formatted.

    Tool Count5/5

    With only 3 tools, the server is tightly scoped to its purpose of providing package ratings. Each tool is necessary and there is no bloat, making the count feel intentional rather than thin.

    Completeness5/5

    The tool surface covers the core workflows: listing available packages, retrieving detailed scores, and requesting background crawls for pre-warming. There are no obvious operational gaps for the stated domain.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources