# Package Health (npm · pkg-health-mcp)

Is this dependency still maintained? Scores npm, PyPI packages and GitHub repos 0-100.

- Trust score: 77/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- npm · `pkg-health-mcp`: 77/100 (this document), [markdown](https://verifymcp.io/servers/orcsnren-pkg-health-mcp/pkg-health-mcp.md), [page](https://verifymcp.io/servers/orcsnren-pkg-health-mcp/pkg-health-mcp)

## Channel facts

- Registry: `npm`
- Package: `pkg-health-mcp`
- Version: `0.2.0`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 30 of 92 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 48/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (Apache-2.0).
  - Actively maintained (last published 13 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 74/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 581 tokens (~193/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 47/100
  - Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Package Health MCP server?

Package Health runs locally as an npm package, launched with npx -y pkg-health-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add orcsnren-pkg-health-mcp -- npx -y pkg-health-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "orcsnren-pkg-health-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "pkg-health-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "orcsnren-pkg-health-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "pkg-health-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add orcsnren-pkg-health-mcp -- npx -y pkg-health-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "orcsnren-pkg-health-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "pkg-health-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add orcsnren-pkg-health-mcp --command npx --arg -y --arg pkg-health-mcp
```

### Hermes

```yaml
mcp_servers:
  orcsnren-pkg-health-mcp:
    command: "npx"
    args: ["-y", "pkg-health-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "orcsnren-pkg-health-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "pkg-health-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add orcsnren-pkg-health-mcp -t stdio -c npx -a -y pkg-health-mcp
```

### Other

```json
{
  "mcpServers": {
    "orcsnren-pkg-health-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "pkg-health-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-02 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-31 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-29 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-27 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-25 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-23 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-22 (score 70)

First indexed and scored.

## MCP tools (3)

### `check_package` (~195 tokens)

Check package health

Score how well an npm or PyPI package, or any GitHub repository, is maintained (0-100, graded A-F). Looks at release and commit recency, number of active committers, time to first maintainer response, issue close time, download trend, OpenSSF Scorecard and license. Use before adding a new dependency, when asked whether a library or project is abandoned, or to vet a GitHub project that is not published to a registry.

Input parameters:

- `ecosystem` (string): Where to look: 'npm' (JavaScript/TypeScript), 'pypi' (Python) or 'github' (any GitHub repository, name given as 'owner/repo'). A GitHub URL or 'owner/repo' is detected automatically.
- `name` (string, required): Package name ('express', '@types/node', 'requests') or GitHub repository ('owner/repo' or a github.com URL)

### `scan_manifest` (~251 tokens)

Scan dependency manifest

Score every dependency in a manifest or lock file and list the riskiest first. Supports package.json, requirements.txt, pyproject.toml, and the lock files package-lock.json, yarn.lock, pnpm-lock.yaml, poetry.lock and uv.lock (which include transitive dependencies). GitHub-hosted dependencies are scored as repositories. Prefer `path` for local files, especially large lock files; otherwise pass `content`. Use to audit a project's dependencies for abandoned or risky packages.

Input parameters:

- `content` (string): Full text of the manifest file, if not passing `path`
- `filename` (string): File name for `content`, used to detect the format (e.g. package.json, yarn.lock)
- `include_dev` (boolean): Also score devDependencies / optional dependencies
- `max_packages` (integer): Upper limit on packages scored; lock files often list several hundred
- `path` (string): Path to a local manifest or lock file, relative to the server's working directory. One of: package.json, requirements.txt, pyproject.toml, package-lock.json, npm-shrinkwrap.json, yarn.lock, pnpm-lock…

### `compare_packages` (~135 tokens)

Compare alternative packages

Compare 2-5 alternative packages from the same registry (e.g. 'moment' vs 'dayjs' vs 'date-fns'), or GitHub repositories, and rank them by maintenance health. Use when choosing between libraries.

Input parameters:

- `ecosystem` (string): Where to look: 'npm' (JavaScript/TypeScript), 'pypi' (Python) or 'github' (any GitHub repository, name given as 'owner/repo'). A GitHub URL or 'owner/repo' is detected automatically.
- `packages` (array, required): Package names or GitHub repositories ('owner/repo') to compare

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/orcsnren-pkg-health-mcp/pkg-health-mcp#diagnostics

## Score history

- 2026-11-05: 77
- 2026-11-04: 76
- 2026-11-03: 76
- 2026-11-02: 76
- 2026-11-01: 75
- 2026-10-31: 75
- 2026-10-30: 74
- 2026-10-29: 74
- 2026-10-28: 73
- 2026-10-27: 73
- 2026-10-26: 72
- 2026-10-25: 72
- 2026-10-24: 71
- 2026-10-23: 71
- 2026-10-22: 70

## Common questions

### What is the Package Health MCP server?

Package Health is an MCP server listed in the public MCP registry as io.github.orcsnren/pkg-health-mcp. Is this dependency still maintained? Scores npm, PyPI packages and GitHub repos 0-100. This page covers its npm package (pkg-health-mcp).

### Is the Package Health MCP server safe to use?

Package Health scores 77 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Package Health MCP server expose?

Package Health exposes 3 tools: check_package, scan_manifest, compare_packages. Their descriptions and schemas cost roughly 581 tokens of context every time the server is loaded.

### Is the Package Health MCP server still maintained?

Package Health is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the Package Health MCP server under?

Package Health declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the Package Health MCP server?

VerifyMCP ran 16 checks on Package Health, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/pkg-health-mcp
- Socket report: https://socket.dev/npm/package/pkg-health-mcp
- Repository: https://github.com/orcsnren/pkg-health-mcp
- Changelog RSS feed: https://verifymcp.io/servers/orcsnren-pkg-health-mcp/pkg-health-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/orcsnren-pkg-health-mcp/pkg-health-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/orcsnren-pkg-health-mcp/pkg-health-mcp.json
- HTML version of this page: https://verifymcp.io/servers/orcsnren-pkg-health-mcp/pkg-health-mcp