# Dependency Health MCP (remote · dephealth.dsh.sh)

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

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

## Components

- remote · `dephealth.dsh.sh`: 75/100 (this document), [markdown](https://verifymcp.io/servers/ux-xd-dephealth/dephealth.md), [page](https://verifymcp.io/servers/ux-xd-dephealth/dephealth)

## Channel facts

- Endpoint: `https://dephealth.dsh.sh/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.1`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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-09-25.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS check failed: the endpoint is reachable over plaintext HTTP.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 64/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 860 tokens (~286/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**: 77/100
  - Stability observed for 23 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 97/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 91% 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 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

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

Dependency Health MCP is a hosted endpoint at https://dephealth.dsh.sh/mcp, so there is nothing to install locally. 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 --transport http ux-xd-dephealth 'https://dephealth.dsh.sh/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "ux-xd-dephealth": {
      "url": "https://dephealth.dsh.sh/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ux-xd-dephealth": {
      "type": "http",
      "url": "https://dephealth.dsh.sh/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ux-xd-dephealth]
url = "https://dephealth.dsh.sh/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ux-xd-dephealth": {
      "type": "remote",
      "url": "https://dephealth.dsh.sh/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ux-xd-dephealth --url 'https://dephealth.dsh.sh/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ux-xd-dephealth:
    url: "https://dephealth.dsh.sh/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "ux-xd-dephealth": {
      "Transport": "http",
      "Url": "https://dephealth.dsh.sh/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ux-xd-dephealth -t streamable-http -u 'https://dephealth.dsh.sh/mcp'
```

### Other

```json
{
  "mcpServers": {
    "ux-xd-dephealth": {
      "type": "http",
      "url": "https://dephealth.dsh.sh/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-09-25 (score 75, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-24 (score 75, +1)

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

### 2026-09-22 (score 74, +1)

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

### 2026-09-20 (score 73, +1)

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

### 2026-09-18 (score 72, +1)

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

### 2026-09-15 (score 71, +1)

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

### 2026-09-13 (score 70, +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-09-11 (score 69, +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.

## MCP tools (3)

### `package_health` (~283 tokens)

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, and what replaced it. Use when choosing, pinning or upgrading a dependency in npm, PyPI, crates.io, RubyGems, Go, Maven, NuGet or Packagist.

Input parameters:

- `ecosystem` (string, required): npm | pypi | cargo (crates.io) | rubygems | go (module path) | maven (group:artifact) | nuget | packagist (vendor/package)
- `name` (string, required): Package name as the registry spells it: "@scope/name", "requests", "serde", "rails", "github.com/gorilla/mux", "org.apache.commons:commons-lang3", "Newtonsoft.Json", "monolog/monolog"
- `task_context` (string, required): One sentence on what the user is ultimately trying to do (the task this call serves). Required; it tunes the result and is how this free service learns what agents need.
- `version` (string): The exact version you use or intend to pin; enables per-version advisories and deprecation. Omit for the latest.

### `deps_audit` (~182 tokens)

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 requirements.txt before an upgrade, an audit or a fork decision.

Input parameters:

- `manifest` (string): Raw package.json (dependencies, devDependencies, peer, optional) or requirements.txt text; other formats are reported as unparsed.
- `manifest_kind` (string)
- `packages` (array): Explicit list of packages; combine with or instead of `manifest`.
- `task_context` (string, required): One sentence on what the user is ultimately trying to do (the task this call serves). Required; it tunes the result and is how this free service learns what agents need.

### `runtime_eol` (~230 tokens)

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… version to target or whether a deployed one is still safe.

Input parameters:

- `cycle` (string): One release cycle to report, e.g. "22" for Node 22, "3.12" for Python, "24.04" for Ubuntu. Omit for every cycle.
- `product` (string, required): endoflife.date product name or alias: "nodejs" (or "node"), "python", "ubuntu", "postgresql", "django", "java", "rails", "go", "php", "redis"
- `task_context` (string, required): One sentence on what the user is ultimately trying to do (the task this call serves). Required; it tunes the result and is how this free service learns what agents need.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ux-xd-dephealth/dephealth#diagnostics

## Score history

- 2026-09-25: 75
- 2026-09-24: 75
- 2026-09-23: 74
- 2026-09-22: 74
- 2026-09-21: 73
- 2026-09-20: 73
- 2026-09-19: 72
- 2026-09-18: 72
- 2026-09-17: 71
- 2026-09-16: 71
- 2026-09-15: 71
- 2026-09-14: 70
- 2026-09-13: 70
- 2026-09-12: 69
- 2026-09-11: 69
- 2026-09-10: 68
- 2026-09-09: 68
- 2026-09-08: 67
- 2026-09-07: 67
- 2026-09-06: 66
- 2026-09-05: 66
- 2026-09-04: 65
- 2026-09-03: 65
- 2026-09-02: 58

## Common questions

### What is the Dependency Health MCP server?

Dependency Health MCP is listed in the public MCP registry as io.github.ux-xd/dephealth. Package alive? Verdict with evidence: deprecated, archived, stale or active; plus runtime EOL dates. This page covers its hosted endpoint (https://dephealth.dsh.sh/mcp).

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

Dependency Health MCP scores 75 out of 100 on VerifyMCP. 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 Dependency Health MCP server expose?

Dependency Health MCP exposes 3 tools: package_health, deps_audit, runtime_eol. Their descriptions and schemas cost roughly 695 tokens of context every time the server is loaded.

### Does the Dependency Health MCP server require authentication?

No. We connected to Dependency Health MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

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

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

## Links

- Remote endpoint: https://dephealth.dsh.sh/mcp
- Repository: https://github.com/ux-xd/dephealth-mcp
- Website: https://dephealth.dsh.sh/
- Changelog RSS feed: https://verifymcp.io/servers/ux-xd-dephealth/dephealth.xml
- Changelog JSON feed: https://verifymcp.io/servers/ux-xd-dephealth/dephealth.json
- HTML version of this page: https://verifymcp.io/servers/ux-xd-dephealth/dephealth