io.github.ux-xd/dephealth · v0.1.1 · developer-tools
Dependency Health MCP is healthy: it completed an MCP handshake in 3049 ms and exposes 3 tools.
Package alive? Verdict with evidence: deprecated, archived, stale or active; plus runtime EOL dates.
Endpoint: https://dephealth.dsh.sh/mcp (streamable-http)
Repository · Website · JSON · Add to my inventory
| Users (last 30 days) | 0 |
| Handshake | Healthy |
| Auth needed | None |
| Tool count | 3 |
| Latency | 3049 ms |
| Last checked (UTC) | 2026-10-15T11:15:15.532Z |
| Checked (UTC) | Status | Latency | Error |
|---|---|---|---|
| 2026-10-15T11:15:15.532Z | Healthy | 3049 |
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 |