io.github.muzimu217/DeliverKit
NPM · DELIVERKIT-MCP
Plan and verify multi-ecosystem packaging (Linux, Windows, macOS, HarmonyOS) for AI agents.
Available components
Last scanned (5 hours ago)
Scores higher than 58% of npm servers
Category CI/CD and DevOps
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
- 32 of 98 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- 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 44 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability73
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1558 tokens (~141/item across 11 items; 11 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 Management93
- Stability observed for 28 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 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 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.
- 4 Nov 26 −1
- Stability: pass → 0.90 functional
- 29 Oct 26 0
- Stability: 0.97 → pass security
- 28 Oct 26 0
- Stability: pass → 0.97 functional
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 19 Oct 26 0
- Security disclosure: unverified → pass ▲ functional
- 18 Oct 26 0
- Stability: 0.97 → pass security
- Security disclosure: pass → unverified ▼ functional
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 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/deliverkit-mcp@0.3.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 98 packages
| Packages resolved | 98 |
|---|---|
| Stale | 32 |
| 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 →
generate_ci_workflow ~128
按已审查的 Forge.md 契约生成 GitHub Actions Linux/Windows 多平台交付工作流；签名材料只通过 CI secrets 注入。
| Name | Type | Req | Description |
|---|---|---|---|
| output_path | string | – | 工作流输出路径，默认 <source_dir>/.github/workflows/deliverkit.yml |
| overwrite | boolean | – | 是否允许覆盖已存在的工作流文件，默认 false |
| plan_path | string | yes | Forge.md 交付契约文件路径（构建类工具必需） |
| source_dir | string | yes | 项目根目录路径 |
No output schema declared.
No examples provided.
generate_packaging_plan ~167
生成项目级 Forge.md 交付契约，记录目标生态、产物、决策依据和风险（计划先行，后续构建工具必须基于此契约）。
| Name | Type | Req | Description |
|---|---|---|---|
| entrypoints | array | – | 手动指定入口列表：项目内相对路径（文件须存在）或 npm start |
| goals | array | yes | 目标产物列表（如 ["deb", "rpm"] 或 ["windows-msi"]） |
| language | string | – | 手动指定项目语言（自动识别失败或识别错误时使用） |
| source_dir | string | yes | 项目根目录路径 |
| target_environment | string | – | 目标环境（如 ubuntu-22.04、windows、macos、harmonyos） |
No output schema declared.
No examples provided.
generate_release_manifest ~120
汇总各平台结构化构建结果、SHA256、签名/安装/运行证据，生成统一 ReleaseManifest.json。
| Name | Type | Req | Description |
|---|---|---|---|
| output_path | string | – | 报告输出路径，默认 <source_dir>/ReleaseManifest.json |
| plan_path | string | yes | Forge.md 交付契约文件路径（构建类工具必需） |
| results_dir | string | – | 平台结果 JSON 目录，默认 <source_dir>/.deliverkit/results |
| source_dir | string | yes | 项目根目录路径 |
No output schema declared.
No examples provided.
get_ecosystem_knowledge ~80
读取某个生态的知识包（产物形态、工具链、签名硬约束、上架规则、验证方法）。缺省 ecosystem 时返回全部已注册生态。
| Name | Type | Req | Description |
|---|---|---|---|
| ecosystem | string | – | 生态 id（如 linux/ubuntu、mobile/harmonyos）；缺省返回全部已注册生态 |
No output schema declared.
No examples provided.
inspect_project ~96
分析项目目录，识别语言、入口和已有打包配置，返回推荐的跨生态交付目标。
| Name | Type | Req | Description |
|---|---|---|---|
| entrypoints | array | – | 手动指定入口列表：项目内相对路径（文件须存在）或 npm start |
| language | string | – | 手动指定项目语言（自动识别失败或识别错误时使用） |
| source_dir | string | yes | 项目根目录路径 |
No output schema declared.
No examples provided.
pack_appimage ~165
按已审查的 Forge.md 契约，在隔离 Ubuntu x86_64 容器中封装 AppImage，并以 extract-and-run 验证。
| Name | Type | Req | Description |
|---|---|---|---|
| output_dir | string | – | 产物输出目录，默认 <source_dir>/.deliverkit/artifacts |
| package_name | string | – | AppImage 名称；缺省时使用项目名 |
| package_version | string | – | 产物版本；缺省时使用 Forge.md 契约中的项目版本（来自项目元数据，最终回退 0.1.0） |
| plan_path | string | yes | Forge.md 交付契约文件路径（构建类工具必需） |
| source_dir | string | yes | 项目根目录路径 |
No output schema declared.
No examples provided.
pack_deb ~163
按已审查的 Forge.md 契约，在隔离 Ubuntu 容器中构建 deb 包，并在干净容器中安装和运行验证。
| Name | Type | Req | Description |
|---|---|---|---|
| output_dir | string | – | 产物输出目录，默认 <source_dir>/.deliverkit/artifacts |
| package_name | string | – | Debian 包名；缺省时使用项目名 |
| package_version | string | – | 产物版本；缺省时使用 Forge.md 契约中的项目版本（来自项目元数据，最终回退 0.1.0） |
| plan_path | string | yes | Forge.md 交付契约文件路径（构建类工具必需） |
| source_dir | string | yes | 项目根目录路径 |
No output schema declared.
No examples provided.
pack_harmonyos ~122
在 Linux/Windows DevEco runner 使用 hvigorw 构建 HAP/APP，并用 hdc 安装验证正式签名产物。
| Name | Type | Req | Description |
|---|---|---|---|
| artifact | string | – | 构建 HAP 或正式 APP，默认按计划选择 |
| output_dir | string | – | 产物输出目录，默认 <source_dir>/.deliverkit/artifacts |
| plan_path | string | yes | Forge.md 交付契约文件路径（构建类工具必需） |
| source_dir | string | yes | 项目根目录路径 |
No output schema declared.
No examples provided.
pack_macos ~194
在 macOS runner 使用 codesign/hdiutil 或 productbuild/productsign 生成 DMG/PKG，调用 notarytool 公证，并以 spctl/stapler 验证。
| Name | Type | Req | Description |
|---|---|---|---|
| artifact | string | – | 构建 DMG 或签名 PKG，默认按计划选择 |
| output_dir | string | – | 产物输出目录，默认 <source_dir>/.deliverkit/artifacts |
| package_name | string | – | DMG/PKG 名称；缺省时使用项目名 |
| package_version | string | – | 产物版本；缺省时使用 Forge.md 契约中的项目版本（来自项目元数据，最终回退 0.1.0） |
| plan_path | string | yes | Forge.md 交付契约文件路径（构建类工具必需） |
| source_dir | string | yes | 项目根目录路径 |
No output schema declared.
No examples provided.
pack_rpm ~164
按已审查的 Forge.md 契约，在隔离 Rocky Linux 容器中构建 rpm 包，并在干净容器中安装和运行验证。
| Name | Type | Req | Description |
|---|---|---|---|
| output_dir | string | – | 产物输出目录，默认 <source_dir>/.deliverkit/artifacts |
| package_name | string | – | RPM 包名；缺省时使用项目名 |
| package_version | string | – | 产物版本；缺省时使用 Forge.md 契约中的项目版本（来自项目元数据，最终回退 0.1.0） |
| plan_path | string | yes | Forge.md 交付契约文件路径（构建类工具必需） |
| source_dir | string | yes | 项目根目录路径 |
No output schema declared.
No examples provided.
pack_windows_msi ~159
在 Windows runner 使用 WiX 生成 MSI，使用 Authenticode 签名，并以 signtool/msiexec 完成安装验证。
| Name | Type | Req | Description |
|---|---|---|---|
| output_dir | string | – | 产物输出目录，默认 <source_dir>/.deliverkit/artifacts |
| package_name | string | – | MSI 名称；缺省时使用项目名 |
| package_version | string | – | 产物版本；缺省时使用 Forge.md 契约中的项目版本（来自项目元数据，最终回退 0.1.0） |
| plan_path | string | yes | Forge.md 交付契约文件路径（构建类工具必需） |
| source_dir | string | yes | 项目根目录路径 |
No output schema declared.
No examples provided.
How do I install the io.github.muzimu217/DeliverKit MCP server?
io.github.muzimu217/DeliverKit runs locally as an npm package, launched with npx -y deliverkit-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · deliverkit-mcp
claude mcp add muzimu217-deliverkit -- npx -y deliverkit-mcp
What is the io.github.muzimu217/DeliverKit MCP server?
io.github.muzimu217/DeliverKit is an MCP server listed in the public MCP registry as io.github.muzimu217/DeliverKit. Plan and verify multi-ecosystem packaging (Linux, Windows, macOS, HarmonyOS) for AI agents. This page covers its npm package (deliverkit-mcp).
Is the io.github.muzimu217/DeliverKit MCP server safe to use?
io.github.muzimu217/DeliverKit scores 78 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.muzimu217/DeliverKit MCP server expose?
io.github.muzimu217/DeliverKit exposes 11 tools: inspect_project, generate_packaging_plan, get_ecosystem_knowledge, pack_deb, pack_rpm, and 6 more. Their descriptions and schemas cost roughly 1,558 tokens of context every time the server is loaded.
Is the io.github.muzimu217/DeliverKit MCP server still maintained?
io.github.muzimu217/DeliverKit 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.muzimu217/DeliverKit MCP server under?
io.github.muzimu217/DeliverKit declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.