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

Packkit

NPM · PACKKIT-MCP · SCANNED AUG 3

Scaffold modern npm packages, CLIs, services and apps as a native tool for AI agents.

Available components

+47 this week 74 Trust /100
Trust breakdown (6 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 →

Supply Chain Security87
  • No malware found by supply-chain analysis.Pass
  • Only part of the dependency tree could be resolved (100 of 104), so this covers what we could see, not the whole tree.Partial
  • No install/post-install scripts declared.Pass
  • Only part of the dependency tree could be resolved (100 of 104), so this covers what we could see, not the whole tree. 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 DanMat/create-packkit). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 7 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability72
  • AI-judged instruction clarity (excellent).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 Management27
  • Stability observed for 8 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
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · packkit-mcp

# add to Claude Code
claude mcp add danmat-packkit-mcp -- npx -y packkit-mcp
# add to Codex CLI
codex mcp add danmat-packkit-mcp -- npx -y packkit-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "danmat-packkit-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "packkit-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add danmat-packkit-mcp --command npx --arg -y --arg packkit-mcp
# ~/.hermes/config.yaml
mcp_servers:
  danmat-packkit-mcp:
    command: "npx"
    args: ["-y", "packkit-mcp"]
// mcp.json
{
  "mcpServers": {
    "danmat-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.

  • 3 Aug 26 +21
    • Source repository: pass → fail security
    • Known CVEs: unverified → partial security
    • Schema quality: unverified → excellent functional
    • Dependency health: unverified → partial functional
    • Stability: unverified → 0.27 functional
    • MCP protocol: unverified → pass functional
  • 2 Aug 26 +5
    • Known CVEs: partial → unverified security
    • Malware scan: unverified → pass security
    • Dependency health: partial → unverified functional
  • 1 Aug 26 +21
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Jul 26 27

    First indexed and scored.

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 3 Aug 2026 · Analysed npm/[email protected]

Provenance verified

Ecosystem: npm · Outcome: verified

Reason: verified

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
Discovery method:
attestation_endpoint
Dependencies 100 packages

100 packages in the resolved dependency tree · 99 deprecated · 29 stale.

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools — 3 exposed · ~496 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.

Tool Tokens
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.

NameTypeReqDescription
namestringyesPackage name
optionsobjectAny options from packkit_schema (e.g. { "framework": "vue", "target": ["library"] })
presetstringA 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.

NameTypeReqDescription
directorystringParent directory to create the project in (default: current working directory)
gitbooleangit init + initial commit (default false)
githubbooleanCreate the repository on GitHub and push to it, using the `gh` CLI. Requires git. Private unless "public" is set.
installbooleanInstall dependencies (default false)
mergebooleanScaffold 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.
namestringyesPackage name (also the folder name)
optionsobjectAny options from packkit_schema
presetstringA preset or alias
publicbooleanWhen 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.