Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Packkit

NPM · PACKKIT-MCP · SCANNED SEP 20

Scaffold and upgrade modern projects (JS/TS, Python) as a native tool for AI agents.

Available components

npm · packkit-mcp 90
0 this week 90 Trust /100
Trust breakdown (7 categories)

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 105 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency71
  • 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 PackkitJS/packkit-mcp). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 33 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability81
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 564 tokens (~112/item across 5 items; 5 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
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 5 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
Install

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

# add to Claude Code
claude mcp add packkitjs-packkit-mcp -- npx -y packkit-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "packkitjs-packkit-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "packkit-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "packkitjs-packkit-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "packkit-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add packkitjs-packkit-mcp -- npx -y packkit-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "packkitjs-packkit-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "packkit-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add packkitjs-packkit-mcp --command npx --arg -y --arg packkit-mcp
# ~/.hermes/config.yaml
mcp_servers:
  packkitjs-packkit-mcp:
    command: "npx"
    args: ["-y", "packkit-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "packkitjs-packkit-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "packkit-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add packkitjs-packkit-mcp -t stdio -c npx -a -y packkit-mcp
// mcp.json
{
  "mcpServers": {
    "packkitjs-packkit-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "packkit-mcp"
      ]
    }
  }
}
Changelog

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 0
    • Stability: 0.97 → pass security
  • 19 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.

  • 17 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.

  • 15 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.

  • 14 Sept 26 −3
    • Security disclosure: unverified → fail ▼ functional
    • Stability: pass → 0.80 functional
  • 13 Sept 26 0
    • Stability: 0.97 → pass security
    • Security disclosure: fail → unverified ▼ functional
  • 12 Sept 26 0
    • Stability: pass → 0.97 functional
  • 11 Sept 26 0
    • Stability: 0.97 → pass security
Diagnostics

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@1.1.0

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 PackkitJS/packkit-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/PackkitJS/packkit-mcp/.github/workflows/release.yml@refs/heads/main
Rekor log index 2469380950
Predicate type https://slsa.dev/provenance/v1
Subject digest sha512:834674070d3292b8386f1a47247b55dc83a3d4f7b2e1b8b70a4c394a33d3b1983db0468e9e8c99985906773e7a37995b2ff9aebb291cd790544de4bd9

Background: How many MCP packages publish verified provenance →

Dependencies 105 packages
Packages resolved 105
Stale 32
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 5 exposed · ~564 tokens

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 →

Tool Tokens
generate_project ~190

Generate a project with a generator. By default it PREVIEWS (returns the file tree, stack summary and deployment contract without touching disk); pass write: true to scaffold the files under <directory>/<name>. Existing files are never overwritten unless force is set. Call list_presets / get_generator_schema first.

NameTypeReqDescription
configobject–Options from get_generator_schema (overrides the preset)
directorystring–Parent directory to create <name>/ in when writing (default: cwd)
forceboolean–Overwrite colliding existing files when writing (default false)
generatorstringyesGenerator id from list_generators
namestringyesProject/package name (also the folder name when writing)
presetstring–A preset (or alias) from list_presets
writeboolean–Write files to disk (default false = preview only)

No output schema declared.

No examples provided.

get_generator_schema ~63

Return a generator's full option schema — every option, its choices and defaults — as JSON. Read this before passing a `config` to generate_project so the options you set are valid for that generator.

NameTypeReqDescription
generatorstringyesGenerator id from list_generators

No output schema declared.

No examples provided.

list_generators ~63

START HERE. Lists every Packkit generator (a language target — e.g. javascript, python, go) with its maturity and protocol capabilities. Pick the generator whose language matches what the user wants, then call list_presets and get_generator_schema for it before generating.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_presets ~108

List the presets a generator offers (e.g. ts-lib, react-lib, node-service for javascript; py-lib, py-cli for python), each with a description and maturity. Experimental presets are hidden unless includeExperimental is true. Choose a preset that matches the shape the user wants instead of guessing.

NameTypeReqDescription
generatorstringyesGenerator id from list_generators (e.g. "javascript", "python", "go")
includeExperimentalboolean–Include experimental presets (default false)

No output schema declared.

No examples provided.

plan_upgrade ~140

Plan a re-scaffold of an existing project against the current templates: a three-way diff (baseline vs on-disk vs freshly generated) that separates template changes from the user's own edits, so nothing is clobbered. Reports the plan only — it writes nothing. Requires a generator that supports baseline-upgrade.

NameTypeReqDescription
configobject–The options it was generated with
directorystringyesPath to the existing scaffolded project
generatorstringyesGenerator id from list_generators
namestringyesProject name (as originally generated)
presetstring–The preset it was generated from (if any)

No output schema declared.

No examples provided.

Common questions

What is the Packkit MCP server?

Packkit is an MCP server listed in the public MCP registry as io.github.PackkitJS/packkit-mcp. Scaffold and upgrade modern projects (JS/TS, Python) 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 90 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 5 tools: list_generators, list_presets, get_generator_schema, generate_project, plan_upgrade. Their descriptions and schemas cost roughly 564 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.