Skip to main content
Glama
orcsnren

pkg-health-mcp

by orcsnren
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to pkg-health-mcp

No user-submitted related servers found.

    Related Servers

    • 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

    • ossfind

      Aniket-kr1030
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables safety-ranked discovery of open-source components across npm, PyPI, crates.io, RubyGems, GitHub, and Hugging Face, with license, security, and health checks.
      1,348 npm
      MIT

    • jinnexguard-mcp

      ricardorincon719
      A
      license
      Not graded
      quality
      B
      maintenance
      Exposes an assess_repo tool that scans a repository, local folder, or npm/PyPI package and returns supply-chain risk findings with file, line, and code evidence — install-time scripts, dangerous patterns, secrets, AI-agent manipulation, impersonation and published-artifact mismatches — while never executing the target's code. Findings carry severities from info to critical so results can gate installs and CI jobs.
      Apache 2.0

    • pkgtruth

      hxckya
      A
      license
      A
      quality
      A
      maintenance
      Enables AI coding agents and CI to vet npm dependencies before they reach the lockfile, flagging hallucinated, slopsquatted, or otherwise risky packages with evidence-backed verdicts.
      3
      27 npm
      4
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A4.2/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool operates at a clearly different granularity: check_package scores a single package/repo, scan_manifest scores an entire manifest or lock file, and compare_packages ranks 2-5 alternatives from the same registry. The descriptions make these boundaries explicit, so an agent can select correctly without guessing.

    Naming Consistency5/5

    All three tools follow a strict verb_noun snake_case pattern (check_package, scan_manifest, compare_packages). The verbs are also semantically distinct, reinforcing the naming.

    Tool Count5/5

    Three tools is well within the appropriate range and each maps to a distinct user intent: vet one dependency, audit a whole project, or choose between alternatives. No tool feels redundant or padding.

    Completeness4/5

    The surface covers the core lifecycle of package health assessment: single package scoring, bulk manifest auditing, and comparative evaluation. Minor gaps exist, such as retrieving a detailed score breakdown or history for already-scanned dependencies, but these are workarounds an agent can handle via check_package on individual names.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources