Skip to content
MCP server

npm pack checker (what npm publish ships)

Shows exactly which files npm publish ships and the rule behind each one

Runs locally
Install
Pricing
Open source
Platforms
CLI, self-hosted, API
Runs
Locally
Version
1.0.0
Listing updated
today

Similar MCP servers

About npm pack checker (what npm publish ships)

npm pack checker (what npm publish ships) is an open-source MCP server for developer tools. It runs locally on your machine and is started by your AI client.

The README says it reproduces the file list npm 10 produces for a tarball, so you can see what would be published before running npm publish and without touching the registry. For every path it reports whether it ships and which rule decides, whether that is a .npmignore or .gitignore line, a files entry, or npm's built-in defaults.

Beyond the listing, it flags common packaging mistakes: secrets such as .env or keys that would be published because a .npmignore replaced a .gitignore, entries in files or main and bin that will not ship, and tests or coverage output that slipped in. The README describes the engine as a port of npm-packlist and ignore-walk, checked against npm's own output on many generated projects.

It is aimed at Node package maintainers and at AI assistants that prepare packages for release. It runs as a local stdio server, is offline and read-only, and is published under the MIT license.

Install

Run in a terminal

claude mcp add npm-pack-check -- docker run -i --rm ghcr.io/lawatch/npm-pack-check:1.0.0

Add to claude_desktop_config.json

{
  "mcpServers": {
    "npm-pack-check": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/lawatch/npm-pack-check:1.0.0"
      ]
    }
  }
}
Install in CursorOpens Cursor, which asks you to confirm. Or add it by hand:

Add to ~/.cursor/mcp.json

{
  "mcpServers": {
    "npm-pack-check": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/lawatch/npm-pack-check:1.0.0"
      ]
    }
  }
}
Install in VS CodeOpens VS Code, which asks you to confirm. Or add it by hand:

Add to .vscode/mcp.json

{
  "servers": {
    "npm-pack-check": {
      "type": "stdio",
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/lawatch/npm-pack-check:1.0.0"
      ]
    }
  }
}

Add to ~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "npm-pack-check": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/lawatch/npm-pack-check:1.0.0"
      ]
    }
  }
}

Add to your client's MCP settings (most use this shape)

{
  "mcpServers": {
    "npm-pack-check": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/lawatch/npm-pack-check:1.0.0"
      ]
    }
  }
}

Using several servers? Build one config file with the MCP config generator.

Tools this server provides (2)

Taken from the project documentation; the running server may differ.

check_npm_pack
Returns the exact file list of the npm tarball with warnings for secrets, ignore-file conflicts and missing entry points.
why_npm_pack
For each path, states whether it ships and the exact rule that decides it.

What it does

Exact tarball file list
Reproduces the same files and order as npm pack --dry-run from a list of paths and ignore files.
Rule attribution per path
Explains whether each path ships and which .npmignore, .gitignore, files entry or built-in rule decided it.
Secret leak warnings
Warns when sensitive files such as .env or keys would be published.
Missing entry point checks
Flags main, bin, browser or types targets that will not ship, and files entries that match nothing.
Offline and read-only
Runs locally over stdio without file access or publishing to the registry.

Good for

  • Check a package for leaked secrets before running npm publish
  • Understand why a particular file is or is not in the published tarball
  • Catch a main or bin entry point that would break installs for users
  • Give an AI coding assistant a reliable packaging check before release

Pricing

Open source

Free and MIT licensed; run locally.

npm pack checker (what npm publish ships) FAQ

Does it publish anything to npm?

No. The README states it is offline, read-only, and that nothing is published.

How do I install it?

The README lists a Claude Desktop .mcpb file from the GitHub release, a Docker image run over stdio, or running server.js from source with Node 18+.

Which license does it use?

The README says it is released under the MIT license.

What is not modelled?

The README says files added from bundleDependencies are not modelled, and symlinks are not included because npm never ships them.

Is npm pack checker (what npm publish ships) free?

Yes. npm pack checker (what npm publish ships) is open source, so you can use and self-host it for free.

How do I add npm pack checker (what npm publish ships) to Claude Code?

Run this command in your terminal: claude mcp add npm-pack-check -- docker run -i --rm ghcr.io/lawatch/npm-pack-check:1.0.0

What are the best alternatives to npm pack checker (what npm publish ships)?

The closest alternatives to npm pack checker (what npm publish ships) are npm why (who installs this package), npm Registry MCP Server, package.json exports resolver (which file Node loads), unripe and Notary.

Where this comes from

  • Description: written from the project's README and its MCP Registry entry.
  • Install steps: from the official MCP Registry entry.

How AIPoweredBot checks servers