All servers · Health & fitness · Code & repositories · Databases

Dependency Health MCP

io.github.ux-xd/dephealth · v0.1.1

Measured by MCP Station

Last check	Reachable
Checked at	—
Check success 7 / 30 days	—
First-try success 30 days	—
Median response	—
Lookups 30 days	—
Authentication	No auth
MCP version	2025-06-18
Rank score	—
Declared risk	Read-only (all tools declare readOnlyHint)
Capabilities declared	tools
Tool definitions	3 tools · with description 100% · input schema is an object 100% · read/destructive hints 100%

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

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

claude mcp add --transport http dephealth https://dephealth.dsh.sh/mcp

{
  "mcpServers": {
    "dephealth": {
      "url": "https://dephealth.dsh.sh/mcp"
    }
  }
}

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

Repository · Website · JSON · Text for agents · Registry updated 2026-09-02