npm pack checker (what npm publish ships)
MCPB · NPM-PACK-CHECK-1.0.0.MCPB · 2 COMPONENTS
Exact files npm publish ships, which rule decides each, and leaks (.env, keys) to fix first.
Available components
Last scanned (19 hours ago)
Scores higher than 71% of MCPB 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 Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
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 4 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability61
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 778 tokens (~389/item across 2 items; 2 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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 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
Unverified: 2 categories
Categories scored 0 because we could not verify them: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Checks we ran (11)
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (5)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Malware scan in Supply Chain Security (scores 0 for this)No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
- Known CVEs in Supply Chain Security (scores 0 for this)Known CVEs could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).
- Install scripts in Supply Chain Security (scores 0 for this)Install-script risk not yet assessed.
- Dependency health in Supply Chain Security (scores 0 for this)Dependency health could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 16 Nov 26 38
First indexed and scored.
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 21 Nov 2026 · Analysed mcpb/https://github.com/Lawatch/10aday/releases/download/npm-pack-check-v1.0.0/npm-pack-check-1.0.0.mcpb
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | mcpb |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
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_npm_pack Which files will npm publish ship? ~370
Gives the exact file list that `npm pack` / `npm publish` puts in the tarball (npm 10 rules, same order as npm), what is left out, and the warnings that matter before publishing: secrets or .env files that would be published, a .npmignore that silently replaces .gitignore (so git-ignored files get published), "files" entries that match nothing, "main"/"bin"/"browser" pointing to a file that will not be in the package, tests and coverage shipped by mistake. Use it before any publish, when a published package misses files ("Cannot find module" after install) or ships too much. No disk access needed: pass package.json, the file list and the ignore files.
| Name | Type | Req | Description |
|---|---|---|---|
| explain | array | – | Optional: paths to explain one by one (included or not, and which rule decides). |
| ignore_files | object | – | Content of every .npmignore and .gitignore, at any depth, as { "<path>": "<content>" }, e.g. { ".gitignore": "...", "lib/.npmignore": "..." }. They are added to the file list automatically. |
| list_excluded | boolean | – | Also return the list of excluded files (default false: only the count by top folder). |
| package_json | object|string | yes | The root package.json, as an object or as JSON text. |
| paths | array | yes | Every file of the project, relative to the package root, "/" separators. Best: the output of `git ls-files --cached --others` plus untracked build output (e.g. `find . -type f -not -path "./node_modu… |
| Name | Type | Req | Description |
|---|---|---|---|
| excluded | array | – | – |
| excluded_by_folder | object | – | – |
| excluded_count | integer | – | – |
| explained | array | – | – |
| included | array | yes | Files in the tarball, in npm order. |
| included_count | integer | yes | – |
| warnings | array | yes | – |
No examples provided.
why_npm_pack Why is this file (not) in my npm package? ~279
For each path asked, says whether `npm publish` ships it and which exact rule decides: the line of .npmignore or .gitignore (with file and line number), the "files" entry of package.json, or npm's built-in rules (README/LICENSE/package.json always shipped, node_modules/.git/.npmrc/lockfiles never, "main" and "bin" forced in). Also says when a whole folder was skipped.
| Name | Type | Req | Description |
|---|---|---|---|
| explain | array | yes | Paths to explain (they are added to the file list if missing). |
| ignore_files | object | – | Content of every .npmignore and .gitignore, at any depth, as { "<path>": "<content>" }, e.g. { ".gitignore": "...", "lib/.npmignore": "..." }. They are added to the file list automatically. |
| package_json | object|string | yes | The root package.json, as an object or as JSON text. |
| paths | array | – | Every file of the project, relative to the package root, "/" separators. Best: the output of `git ls-files --cached --others` plus untracked build output (e.g. `find . -type f -not -path "./node_modu… |
| Name | Type | Req | Description |
|---|---|---|---|
| explained | array | yes | – |
No examples provided.
How do I install the npm pack checker (what npm publish ships) MCP server?
npm pack checker (what npm publish ships) ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, 1f5750a76c149911a59930cd74e989fef9429efdb335fd56231d82a1bb7c0743; the commands to do that are on this page. If it does not match, do not open it.
mcpb · npm-pack-check-1.0.0.mcpb
Download bundleCheck the download matches the SHA-256 the MCP registry declares before you open it. If it does not match, do not open the file.
SHA-256
1f5750a76c149911a59930cd74e989fef9429efdb335fd56231d82a1bb7c0743
macOS / Linux
echo "1f5750a76c149911a59930cd74e989fef9429efdb335fd56231d82a1bb7c0743 npm-pack-check-1.0.0.mcpb" | shasum -a 256 -c
Windows (PowerShell)
(Get-FileHash -Algorithm SHA256 .\npm-pack-check-1.0.0.mcpb).Hash -eq "1f5750a76c149911a59930cd74e989fef9429efdb335fd56231d82a1bb7c0743"
Run it in the folder you saved the bundle to, then open the file with an MCPB-capable host such as Claude Desktop.
What is the npm pack checker (what npm publish ships) MCP server?
npm pack checker (what npm publish ships) is an MCP server listed in the public MCP registry as io.github.Lawatch/npm-pack-check. Exact files npm publish ships, which rule decides each, and leaks (.env, keys) to fix first. This page covers its MCPB bundle (https://github.com/Lawatch/10aday/releases/download/npm-pack-check-v1.0.0/npm-pack-check-1.0.0.mcpb).
Is the npm pack checker (what npm publish ships) MCP server safe to use?
npm pack checker (what npm publish ships) scores 38 out of 100 on VerifyMCP. 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 npm pack checker (what npm publish ships) MCP server expose?
npm pack checker (what npm publish ships) exposes 2 tools: check_npm_pack, why_npm_pack. Their descriptions and schemas cost roughly 649 tokens of context every time the server is loaded.
What licence is the npm pack checker (what npm publish ships) MCP server under?
npm pack checker (what npm publish ships) declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the npm pack checker (what npm publish ships) MCP server?
VerifyMCP ran 11 checks on npm pack checker (what npm publish ships), covering Source repository, Provenance, License, Maintenance and 7 more. 5 items could not be completed, a gap on our side rather than a finding about npm pack checker (what npm publish ships): Malware scan, Known CVEs, Install scripts, Dependency health and 1 more. 2 categories score 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an MCPB bundle, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.