Packkit
NPM · PACKKIT-MCP · SCANNED SEP 20
Scaffold modern npm packages, CLIs, services and apps as a native tool for AI agents.
Available components
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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 32 of 101 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency74
- Repository check failed: the declared repository URL redirects; it must resolve directly. See how to fix → View diagnostics → Fail
- Cryptographically verified build provenance (signed, bound to DanMat/create-packkit). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 33 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 496 tokens (~165/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 Management90
- Stability observed for 27 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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
How do I install the Packkit MCP server?
Packkit runs locally as an npm package, launched with npx -y packkit-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 · packkit-mcp
claude mcp add danmat-packkit-mcp -- npx -y packkit-mcp
{
"mcpServers": {
"danmat-packkit-mcp": {
"command": "npx",
"args": [
"-y",
"packkit-mcp"
]
}
}
} {
"servers": {
"danmat-packkit-mcp": {
"command": "npx",
"args": [
"-y",
"packkit-mcp"
]
}
}
} codex mcp add danmat-packkit-mcp -- npx -y packkit-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"danmat-packkit-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"packkit-mcp"
],
"enabled": true
}
}
} openclaw mcp add danmat-packkit-mcp --command npx --arg -y --arg packkit-mcp
mcp_servers:
danmat-packkit-mcp:
command: "npx"
args: ["-y", "packkit-mcp"] {
"McpServers": {
"danmat-packkit-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"packkit-mcp"
]
}
}
} assistant mcp add danmat-packkit-mcp -t stdio -c npx -a -y packkit-mcp
{
"mcpServers": {
"danmat-packkit-mcp": {
"command": "npx",
"args": [
"-y",
"packkit-mcp"
]
}
}
} 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.
- 20 Sept 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.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −3
- Stability: pass → 0.77 functional
- 15 Sept 26 0
- Stability: 0.97 → pass security
- 14 Sept 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.
- 12 Sept 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.
- 10 Sept 26 −2
- Stability: pass → 0.83 functional
- 9 Sept 26 0
- Stability: 0.97 → pass security
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 20 Sept 2026 · Analysed npm/packkit-mcp@0.2.2
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | DanMat/create-packkit |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/DanMat/create-packkit/.github/workflows/release.yml@refs/heads/main |
| Rekor log index | 2256404887 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:7c70f655e3ed6d38d5b2c392ba48a444944e790493a30d07c924489ede736a152f448b220824e144254a7db2b94ea42c5ef579201f07351473271d392 |
Background: How many MCP packages publish verified provenance →
Dependencies 101 packages
| Packages resolved | 101 |
|---|---|
| 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 →
packkit_preview ~140
Show the project structure a config would produce — the full file tree and stack summary — without writing anything. Use this to check the layout before committing to it, and to show the user what they are about to get. Cheap and side-effect free, so prefer it over scaffolding to a throwaway directory to see what happens.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Package name |
| options | object | – | Any options from packkit_schema (e.g. { "framework": "vue", "target": ["library"] }) |
| preset | string | – | A preset or alias (e.g. ts-lib, react-lib, node-service, rlib) |
No output schema declared.
No examples provided.
packkit_scaffold ~274
Generate a project to disk. Writes files under <directory>/<name> (or ./<name>), optionally runs git init, installs dependencies, and creates the GitHub repository. Call packkit_schema first if you have not already — picking the preset by guess is how projects end up the wrong shape. If the target directory already has files in it (an existing clone, for instance), pass merge: true rather than failing.
| Name | Type | Req | Description |
|---|---|---|---|
| directory | string | – | Parent directory to create the project in (default: current working directory) |
| git | boolean | – | git init + initial commit (default false) |
| github | boolean | – | Create the repository on GitHub and push to it, using the `gh` CLI. Requires git. Private unless "public" is set. |
| install | boolean | – | Install dependencies (default false) |
| merge | boolean | – | Scaffold into a non-empty directory. Existing files are never overwritten — colliding ones are skipped and reported. Use this when the target is an already-cloned repo. |
| name | string | yes | Package name (also the folder name) |
| options | object | – | Any options from packkit_schema |
| preset | string | – | A preset or alias |
| public | boolean | – | When creating the repository, make it public (default: private) |
No output schema declared.
No examples provided.
packkit_schema ~82
START HERE. Returns every Packkit option, preset, and shortcut alias as JSON. Call this before scaffolding so you pick a preset that matches what the user actually wants — presets range from single libraries to CLIs, HTTP services, SPAs, and full-stack monorepos, and guessing without reading them is the main cause of scaffolding the wrong shape.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the Packkit MCP server?
Packkit is an MCP server listed in the public MCP registry as io.github.DanMat/packkit-mcp. Scaffold modern npm packages, CLIs, services and apps as a native tool for AI agents. This page covers its npm package (packkit-mcp).
Is the Packkit MCP server safe to use?
Packkit scores 88 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Packkit MCP server expose?
Packkit exposes 3 tools: packkit_schema, packkit_preview, packkit_scaffold. Their descriptions and schemas cost roughly 496 tokens of context every time the server is loaded.
Is the Packkit MCP server still maintained?
Packkit is still listed as active in the MCP registry. We last reached this channel on 20 September 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 Packkit MCP server under?
Packkit declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.