Skip to main content
Glama
Sign In
packagerating MCP Server

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-health-mcp

      orcsnren
      A
      license
      A
      quality
      A
      maintenance
      Scores npm packages, PyPI packages and GitHub repositories 0-100 with an A-F grade and plain-language risks. Scans package.json, requirements.txt and lock files; no API key needed.
      3
      109 npm
      1
      Apache 2.0

    • pkg-health-mcp

      actions-marketplace-validations
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents and developers to score npm packages, PyPI packages, and GitHub repositories for maintenance health, producing A–F grades, per-signal details, and plain-language risk lists before adoption. It supports checking individual packages, scanning manifests or lock files for transitive dependencies, and comparing alternatives.
      3
      109 npm
      Apache 2.0

    • pkg-intel-mcp

      JanMaa
      A
      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
      MIT

    • Dependency Health MCP

      superbot-helper
      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
    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

    ActivitySlowing
    ResponsivenessNo issues

    Resources