Package Health
NPM · PKG-HEALTH-MCP
Is this dependency still maintained? Scores npm, PyPI packages and GitHub repos 0-100.
Available components
Last scanned (9 hours ago)
Scores higher than 55% of npm servers
Category Developer Tools
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. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 13 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability74
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management47
- Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +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.
- 2 Nov 26 +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.
- 31 Oct 26 +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.
- 29 Oct 26 +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.
- 27 Oct 26 +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.
- 25 Oct 26 +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.
- 23 Oct 26 +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.
- 22 Oct 26 70
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/pkg-health-mcp@0.2.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_package Check package health ~195
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Package name ('express', '@types/node', 'requests') or GitHub repository ('owner/repo' or a github.com URL) |
No output schema declared.
No examples provided.
compare_packages Compare alternative packages ~135
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Package names or GitHub repositories ('owner/repo') to compare |
No output schema declared.
No examples provided.
scan_manifest Scan dependency manifest ~251
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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… |
No output schema declared.
No examples provided.
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.
npm · pkg-health-mcp
claude mcp add orcsnren-pkg-health-mcp -- npx -y pkg-health-mcp
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.