io.github.feely0208/mcp-dsh-plugins
NPM · @DEEPWHALE-CN/MCP-DSH-PLUGINS
深鲸 DSH 插件市场 MCP 服务器：搜索、查看、校验 51 个深鲸 DSH 插件的版本、兼容性与安装命令。
Available components
Last scanned (1 hour ago)
Scores higher than 46% of npm servers
Category Developer Tools
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 15 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 519 tokens (~129/item across 4 items; 4 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 Management53
- Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 5 Nov 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.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 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.
- 29 Oct 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.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 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 5 Nov 2026 · Analysed npm/@deepwhale-cn/mcp-dsh-plugins@0.1.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
check_runtime 检查 DSH 运行时兼容性 ~104
传入当前 DSH 版本号（支持预发布版本，例如 0.2.1-rc.2），按每个插件最新版本的 engines.dsh 范围判断兼容性，返回兼容 / 不兼容 / 无法判断的插件列表及安装命令。
| Name | Type | Req | Description |
|---|---|---|---|
| dsh_version | string | yes | 当前 DSH 版本号，例如 0.2.1-rc.2 或 0.1.0 |
No output schema declared.
No examples provided.
get_plugin 查看插件详情 ~105
按包名获取单个深鲸 DSH 插件的详情：中英文标题与描述、作者、主页、全部版本、最新版本、DSH 兼容范围，以及安装命令（dsh plugin add <name>）。包名可省略 @deepwhale-cn/ 前缀，例如 dsh-sbom。
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | 插件包名，例如 @deepwhale-cn/dsh-sbom 或 dsh-sbom |
No output schema declared.
No examples provided.
list_categories 列出插件分类 ~85
列出深鲸 DSH 插件市场的分类（合规 / 治理 / 数据 / 供应链 / 能力 / 行业）及每个分类下的插件包名与数量，可用于后续按分类检索。
| Name | Type | Req | Description |
|---|---|---|---|
| include_plugins | boolean | – | 是否在响应中包含每个分类下的插件包名列表（默认 true） |
No output schema declared.
No examples provided.
search_plugins 搜索 DSH 插件 ~144
按关键词模糊搜索深鲸 DSH 插件市场（匹配包名、中英文标题、描述），可按分类过滤。不传 query 时按分类/默认顺序列出插件。返回插件名、简介、最新版本、DSH 兼容范围与安装命令。
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | 分类 id 或中文名，例如 compliance / 合规、data / 数据、supply-chain / 供应链 |
| limit | integer | – | 最多返回条数（1-50，默认 10） |
| query | string | – | 搜索关键词，例如 "sbom"、"隐私"、"供应链" |
No output schema declared.
No examples provided.
How do I install the io.github.feely0208/mcp-dsh-plugins server?
io.github.feely0208/mcp-dsh-plugins runs locally as an npm package, launched with npx -y @deepwhale-cn/mcp-dsh-plugins. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @deepwhale-cn/mcp-dsh-plugins
claude mcp add feely0208-mcp-dsh-plugins -- npx -y @deepwhale-cn/mcp-dsh-plugins
What is the io.github.feely0208/mcp-dsh-plugins server?
io.github.feely0208/mcp-dsh-plugins is listed in the public MCP registry as io.github.feely0208/mcp-dsh-plugins. 深鲸 DSH 插件市场 MCP 服务器：搜索、查看、校验 51 个深鲸 DSH 插件的版本、兼容性与安装命令。 This page covers its npm package (@deepwhale-cn/mcp-dsh-plugins).
Is the io.github.feely0208/mcp-dsh-plugins server safe to use?
io.github.feely0208/mcp-dsh-plugins scores 73 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 2026. It declares no install or post-install scripts. 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 io.github.feely0208/mcp-dsh-plugins server expose?
io.github.feely0208/mcp-dsh-plugins exposes 4 tools: search_plugins, get_plugin, list_categories, check_runtime. Their descriptions and schemas cost roughly 438 tokens of context every time the server is loaded.
Is the io.github.feely0208/mcp-dsh-plugins server still maintained?
io.github.feely0208/mcp-dsh-plugins is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.feely0208/mcp-dsh-plugins server under?
io.github.feely0208/mcp-dsh-plugins declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.