Skip to main content
Glama

Related Servers

Alternatives to pkg-health-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      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
      44 npm
      1
      Apache 2.0
    • 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
    • A
      license
      Not graded
      quality
      F
      maintenance
      Open source intelligence for AI agents — GitHub project-health scoring, package dependency-risk analysis, trending repositories, license checks, and side-by-side package comparison.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding agents to check package names and versions for allow/warn/deny verdicts, scan project lockfiles for known-malicious packages and critical advisories, and suggest safe versions across npm, PyPI, crates.io, and Go before manifests are edited.
      18 npm
      MIT

    TDQS

    A4.2/5.0

    Scored across 3 tools

    Disambiguation5/5

    The three tools have clearly distinct scopes: single-package/repository scoring, manifest-wide dependency scanning, and multi-package comparison. There is little risk of misselection because each maps to a different user intent.

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb_noun pattern: check_package, scan_manifest, compare_packages. The verbs accurately communicate the action and no naming conventions are mixed.

    Tool Count5/5

    Three tools are well-matched to this focused package-health domain: one for individual checks, one for manifest audits, and one for comparisons. Each tool earns its place without redundancy.

    Completeness4/5

    The surface covers the core lifecycle of package-health assessment: checking a single package or repository, auditing a manifest or lock file, and comparing alternatives. Minor gaps exist around richer reporting or detailed per-metric drill-down, but agents can work around them.