Dependency Health MCP

io.github.ux-xd由 GitHub 账号 ux-xd 发布v0.1.1更新于 Oct 24, 2026

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

已验证Streamable HTTP可网页运行开发者工具安全与监控

概览

AI 生成的概览

一个远程 MCP 服务器，让助手查询八种生态系统中软件包的依赖健康状况，以及运行时和操作系统的生命周期终止日期。

可以做什么
检查单个软件包是否已弃用、已归档、已停滞，查询指定版本的公告和建议的替代品，覆盖 npm、PyPI、crates.io、RubyGems、Go、Maven、NuGet 和 Packagist。一次调用审计整个 package.json 或 requirements.txt，或最多 25 个软件包的显式列表，给出每个软件包的结论和汇总。查询运行时、操作系统、数据库或框架版本的支持与终止日期，包括最新补丁、LTS 标记和距终止的天数。
适用场景
在固定、升级、分叉或审计依赖之前使用，或在决定选用哪个 Node、Python、Ubuntu、PostgreSQL 等版本、或判断已部署版本是否仍受支持时使用。
运行要求
远程 Streamable HTTP 端点；无需账户、API 密钥或身份验证。需要能访问该服务器及其上游注册表的网络。每次工具调用都必须提供一句描述用户目标的 task_context。
安装前请注意
task_context 字段被描述为该免费服务了解智能体需求的方式，应视为发送给第三方的数据，避免填入机密或敏感信息。它不是漏洞扫描器、许可证合规工具或流行度排名，也无法查看私有注册表或随源码附带的代码。所有工具均为只读。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Dependency Health MCP，将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Web executable，通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体，或 SourceWeft 对话中。智能体会读取该服务器的安装指南，先向你展示发布者、端点和登录方式，经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/io.github.ux-xd%2Fdephealth/install.md，并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前，先告诉我它的发布者、端点和登录方式，等我确认。不要把 API 密钥写进命令或我会提交的文件；问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。

{
  "mcpServers": {
    "dependency-health": {
      "type": "http",
      "url": "https://dephealth.dsh.sh/mcp"
    }
  }
}

README

Dependency Health MCP

Package alive? Verdict with evidence: deprecated, archived, stale or active; plus runtime EOL dates. Remote MCP server over Streamable HTTP at https://dephealth.dsh.sh/mcp. Free, no API key. Tools: package_health, deps_audit, runtime_eol. The tool list is fixed per version.

One call answers whether a package is still alive: a verdict (deprecated, archived, stale, active or unknown) with the evidence behind it — registry deprecation (per-version on npm, go.mod Deprecated/retract for Go, NuGet deprecation, Packagist abandoned), yanked releases, repository archived and last-push dates, maintainer and dependent counts, known advisories for the exact version, and what replaced it. Covers npm, PyPI, crates.io, RubyGems, Go modules, Maven, NuGet and Packagist through ecosyste.ms, the native registries and deps.dev, all keyless. deps_audit takes a whole package.json or requirements.txt (up to 25 packages) and runtime_eol reports endoflife.date support and EOL dates for runtimes and OSes. Free, no key, no account; every response lists the upstream calls it made.

Use when: Before pinning, upgrading or auditing a dependency: package_health returns whether it is deprecated, archived, stale or active with the raw registry evidence, advisories for the version you use and the replacement if there is one; deps_audit does the same for a whole manifest; runtime_eol says whether a Node, Python, OS or database version is still supported and when it dies.

Not for: Not a vulnerability scanner (advisory ids only, no CVSS triage or reachability), not license compliance, not a popularity ranking, and it cannot see private registries or vendored code.

Quick install (Claude Code): claude mcp add --transport http dephealth https://dephealth.dsh.sh/mcp -s user

Live server: https://dephealth.dsh.sh

Docs

Upstreams

Optional

Tools

ToolPurposeEffects
package_healthIs 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.read-only, open-world, idempotent
deps_auditHealth 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.read-only, open-world, idempotent
runtime_eolSupport 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.read-only, open-world, idempotent

Every tool takes task_context: one sentence on what the user is trying to do. It is required.

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

Input schema:

json
{  "$schema": "http://json-schema.org/draft-07/schema#",  "type": "object",  "properties": {    "ecosystem": {      "type": "string",      "enum": [        "npm",        "pypi",        "cargo",        "rubygems",        "go",        "maven",        "nuget",        "packagist"      ],      "description": "npm | pypi | cargo (crates.io) | rubygems | go (module path) | maven (group:artifact) | nuget | packagist (vendor/package)"    },    "name": {      "type": "string",      "minLength": 1,      "maxLength": 200,      "description": "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\""    },    "version": {      "description": "The exact version you use or intend to pin; enables per-version advisories and deprecation. Omit for the latest.",      "type": "string",      "maxLength": 80    },    "task_context": {      "type": "string",      "minLength": 1,      "maxLength": 500,      "description": "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."    }  },  "required": [    "ecosystem",    "name",    "task_context"  ],  "additionalProperties": false}

Example arguments:

json
{  "ecosystem": "npm",  "name": "request",  "task_context": "example: Is this package alive? One verdict — deprecated, archived, s"}

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

Input schema:

json
{  "$schema": "http://json-schema.org/draft-07/schema#",  "type": "object",  "properties": {    "packages": {      "description": "Explicit list of packages; combine with or instead of `manifest`.",      "maxItems": 25,      "type": "array",      "items": {        "type": "object",        "properties": {          "ecosystem": {            "type": "string",            "enum": [              "npm",              "pypi",              "cargo",              "rubygems",              "go",              "maven",              "nuget",              "packagist"            ],            "description": "npm | pypi | cargo (crates.io) | rubygems | go (module path) | maven (group:artifact) | nuget | packagist (vendor/package)"          },          "name": {            "type": "string",            "minLength": 1,            "maxLength": 200,            "description": "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\""          },          "version": {            "type": "string",            "maxLength": 80          }        },        "required": [          "ecosystem",          "name"        ],        "additionalProperties": false      }    },    "manifest": {      "description": "Raw package.json (dependencies, devDependencies, peer, optional) or requirements.txt text; other formats are reported as unparsed.",      "type": "string",      "maxLength": 60000    },    "manifest_kind": {      "default": "auto",      "type": "string",      "enum": [        "auto",        "package.json",        "requirements.txt"      ]    },    "task_context": {      "type": "string",      "minLength": 1,      "maxLength": 500,      "description": "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."    }  },  "required": [    "manifest_kind",    "task_context"  ],  "additionalProperties": false}

Example arguments:

json
{  "manifest": "{\"dependencies\":{\"request\":\"^2.88.2\",\"lodash\":\"4.17.20\",\"left-pad\":\"^1.3.0\"}}",  "task_context": "example: Health verdict for every package in a manifest or a list, in"}

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

Input schema:

json
{  "$schema": "http://json-schema.org/draft-07/schema#",  "type": "object",  "properties": {    "product": {      "type": "string",      "minLength": 1,      "maxLength": 60,      "description": "endoflife.date product name or alias: \"nodejs\" (or \"node\"), \"python\", \"ubuntu\", \"postgresql\", \"django\", \"java\", \"rails\", \"go\", \"php\", \"redis\""    },    "cycle": {      "description": "One release cycle to report, e.g. \"22\" for Node 22, \"3.12\" for Python, \"24.04\" for Ubuntu. Omit for every cycle.",      "type": "string",      "maxLength": 30    },    "task_context": {      "type": "string",      "minLength": 1,      "maxLength": 500,      "description": "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."    }  },  "required": [    "product",    "task_context"  ],  "additionalProperties": false}

Example arguments:

json
{  "product": "nodejs",  "cycle": "22",  "task_context": "example: Support and end-of-life dates for a runtime, OS, database or"}

Install

Endpoint: https://dephealth.dsh.sh/mcp (Streamable HTTP, MCP 2026-07-28 with 2025-era fallback). Authentication: none.

Claude Code
claude mcp add --transport http dephealth https://dephealth.dsh.sh/mcp -s user
Cursor (~/.cursor/mcp.json)
json
{  "mcpServers": {    "dephealth": {      "url": "https://dephealth.dsh.sh/mcp"    }  }}
VS Code / Copilot (user mcp.json)
json
{  "servers": {    "dephealth": {      "type": "http",      "url": "https://dephealth.dsh.sh/mcp"    }  }}

or code --add-mcp '{"name":"dephealth","type":"http","url":"https://dephealth.dsh.sh/mcp"}'

Claude Desktop / claude.ai

Settings → Connectors → Add custom connector → URL https://dephealth.dsh.sh/mcp, Authentication: None.

ChatGPT

Settings → Connectors → Add custom connector → https://dephealth.dsh.sh/mcp. Desktop app / Codex share ~/.codex/config.toml:

toml
[mcp_servers.dephealth]url = "https://dephealth.dsh.sh/mcp"
Codex CLI (~/.codex/config.toml)
toml
[mcp_servers.dephealth]url = "https://dephealth.dsh.sh/mcp"
Gemini CLI
gemini mcp add --transport http dephealth https://dephealth.dsh.sh/mcp -s user

(settings.json uses httpUrl, not url.)

Windsurf (~/.codeium/windsurf/mcp_config.json)
json
{  "mcpServers": {    "dephealth": {      "serverUrl": "https://dephealth.dsh.sh/mcp"    }  }}
Cline
json
{  "mcpServers": {    "dephealth": {      "type": "streamableHttp",      "url": "https://dephealth.dsh.sh/mcp"    }  }}
Continue (.continue/mcpServers/dephealth.yaml)
yaml
name: dephealthmcpServers:  - name: dephealth    type: streamable-http    url: https://dephealth.dsh.sh/mcp
Zed (settings.json)
json
{  "context_servers": {    "dephealth": {      "source": "custom",      "command": "npx",      "args": [        "-y",        "mcp-remote",        "https://dephealth.dsh.sh/mcp"      ]    }  }}
Any MCP client

Streamable HTTP endpoint: https://dephealth.dsh.sh/mcp

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

This page documents a server. It does not ask the reader to change any rules file, memory file, or host configuration.

Run it yourself

npm install && npm start            # http://127.0.0.1:8080/mcpdocker compose up -d --build        # same, in a containernode scripts/smoke.mjs http://127.0.0.1:8080 package_health '{}'

Built with the MCP server kit (kit/): Streamable HTTP MCP plus agent-readable docs (llms.txt, server.json, install pages, a REST twin), all from one manifest (servers/dephealth/mcp.factory.json). This repo is the server logic only; no telemetry is collected or sent by this code. MIT.

来源：README.md，提交 9392a2f

工具

3

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

输入参数name必填versionecosystem必填task_context必填

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

输入参数manifestpackagestask_context必填manifest_kind

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

输入参数cycleproduct必填task_context必填

版本历史

1
  1. v0.1.1最新Sep 16, 2026

评分

已满足适用检查项的 100%

该评分衡量此收录条目的完整程度，依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价，也不表示服务器安全或当前可用：可连通性是带日期的检查结果，评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分
  • 已声明认证方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分