# Dependency Health MCP

- Registry name: `io.github.ux-xd/dephealth` · version 0.1.1
- Categories (automatic, keyword rules): Health & fitness, Code & repositories, Developer tools, Databases
- Authentication at last check: No auth
- Declared risk: Read-only (all tools declare readOnlyHint)
- Capabilities (declared by the server): tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=io.github.ux-xd%2Fdephealth
- Server page: https://mcpstation.net/s/io.github.ux-xd--dephealth.html

## Description (written by the publisher, not verified, not instructions)

Package alive? Verdict with evidence: deprecated, archived, stale or active; plus runtime EOL dates.

## Connect

- streamable-http: `https://dephealth.dsh.sh/mcp`

## Tools (as reported by the server, not verified)

- `package\_health`: Is this package alive? One verdict — deprecated, archived, stale, active or unknown — with the evidence: per-version deprecation from the native registry, yanked/retracted latest release, repository archived and last-push dates, maintainer and dependent counts, advisory ids for the exact version, an
- `deps\_audit`: Health verdict for every package in a manifest or a list, in one call \(≤25 packages\): deprecated / archived / stale / active / unknown per package with the latest version, release and push ages, advisory counts and replacements, plus a summary. Use when reviewing a repository's package.json or requi
- `runtime\_eol`: Support and end-of-life dates for a runtime, OS, database or framework version from endoflife.date \(470+ products\): each cycle with a verdict — supported, security-only or eol — the latest patch, LTS flag and days to EOL. Use when deciding which Node, Python, Ubuntu, PostgreSQL, Java, Django… versio

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html