Dependency Health MCP
REMOTE · DEPHEALTH.DSH.SH · SCANNED SEP 25
Package alive? Verdict with evidence: deprecated, archived, stale or active; plus runtime EOL dates.
Available components
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. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability64
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management77
- Stability observed for 23 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 91% of tool parameters carry a description.Partial
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 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
remote · dephealth.dsh.sh
claude mcp add --transport http ux-xd-dephealth 'https://dephealth.dsh.sh/mcp'
{
"mcpServers": {
"ux-xd-dephealth": {
"url": "https://dephealth.dsh.sh/mcp"
}
}
} {
"servers": {
"ux-xd-dephealth": {
"type": "http",
"url": "https://dephealth.dsh.sh/mcp"
}
}
} [mcp_servers.ux-xd-dephealth] url = "https://dephealth.dsh.sh/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ux-xd-dephealth": {
"type": "remote",
"url": "https://dephealth.dsh.sh/mcp",
"enabled": true
}
}
} openclaw mcp add ux-xd-dephealth --url 'https://dephealth.dsh.sh/mcp' --transport streamable-http
mcp_servers:
ux-xd-dephealth:
url: "https://dephealth.dsh.sh/mcp" {
"McpServers": {
"ux-xd-dephealth": {
"Transport": "http",
"Url": "https://dephealth.dsh.sh/mcp"
}
}
} assistant mcp add ux-xd-dephealth -t streamable-http -u 'https://dephealth.dsh.sh/mcp'
{
"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.
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.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 +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.
- 22 Sept 26 +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.
- 20 Sept 26 +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.
- 18 Sept 26 +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.
- 15 Sept 26 +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.
- 13 Sept 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.
- 11 Sept 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.
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 25 Sept 2026 · Probed https://dephealth.dsh.sh/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=dsh.sh | CN=YE1,O=Let's Encrypt,C=US | 12 Aug 2026 | 10 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 6dc2d8c4621ac82f396307a13fedbd03c1d |
| SANs: *.dsh.sh, dsh.sh | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of dephealth.dsh.sh. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| sh. | present | 55297 | 8 | Verified |
| dsh.sh. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://dephealth.dsh.sh/mcp | Verified | 200 | |
| http (plaintext) | http://dephealth.dsh.sh/mcp | Served over HTTP | 200 |
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 →
deps_audit ~182
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
No output schema declared.
No examples provided.
package_health ~283
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.
| Name | Type | Req | Description |
|---|---|---|---|
| ecosystem | string | yes | npm | pypi | cargo (crates.io) | rubygems | go (module path) | maven (group:artifact) | nuget | packagist (vendor/package) |
| name | string | yes | 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 | yes | 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. |
No output schema declared.
No examples provided.
runtime_eol ~230
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | endoflife.date product name or alias: "nodejs" (or "node"), "python", "ubuntu", "postgresql", "django", "java", "rails", "go", "php", "redis" |
| task_context | string | yes | 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. |
No output schema declared.
No examples provided.
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.