# Npm (npm · @pipeworx/mcp-npm)

npm MCP — wraps the npm Registry API (free, no auth)

- Trust score: 85/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 77/100, [markdown](https://verifymcp.io/servers/pipeworx-io-npm/npm-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-npm/npm-mcp)
- npm · `@pipeworx/mcp-npm`: 85/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-npm/pipeworx-mcp-npm.md), [page](https://verifymcp.io/servers/pipeworx-io-npm/pipeworx-mcp-npm)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-npm`
- Version: `0.2.1`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-npm).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 1 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 80/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 569 tokens (~113/item across 5 items; 5 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Npm MCP server?

Npm runs locally as an npm package, launched with npx -y @pipeworx/mcp-npm. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add pipeworx-io-npm -- npx -y @pipeworx/mcp-npm
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-npm": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-npm"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-npm": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-npm"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-npm -- npx -y @pipeworx/mcp-npm
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-npm": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-npm"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-npm --command npx --arg -y --arg @pipeworx/mcp-npm
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-npm:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-npm"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-npm": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-npm"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-npm -t stdio -c npx -a -y @pipeworx/mcp-npm
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-npm": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-npm"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 85, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-11-03 (score 69, −15)

- [security regression] Malware scan: pass → unverified
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-11-02 (score 84, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-31 (score 83, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-29 (score 82)

First indexed and scored.

## MCP tools (5)

### `search_packages` (~69 tokens)

Search npm for packages by keyword. Returns package names, descriptions, latest versions, publish dates, and publishers. Use when discovering libraries for a task.

Input parameters:

- `limit` (number): Maximum number of results to return (default 10, max 50)
- `query` (string, required): Search query string

### `get_package` (~58 tokens)

Get full details for a specific package: version, description, dependencies, homepage, repository, and license. Use after search_packages to evaluate a candidate package.

Input parameters:

- `name` (string, required): Exact package name (e.g., "express", "lodash")

### `get_downloads` (~114 tokens)

Fetch npm download counts for a package over a named period (last-day, last-week, last-month, last-year) or a custom date range like "2024-01-01:2024-06-30". Returns total downloads, start date, and end date.

Input parameters:

- `name` (string, required): Package name
- `period` (string): Download period: last-day, last-week (default), last-month, or a date range like 2024-01-01:2024-06-30

### `list_versions` (~115 tokens)

List published versions of an npm package with publish dates, dist-tags (latest/next/beta), and deprecation notices — answers "what versions of <pkg> exist", "when was <pkg> last published", "is the latest version deprecated". Returns versions newest-first, plus the package created/last-modified timestamps.

Input parameters:

- `limit` (number): Number of recent versions to return (default 20, max 100).
- `name` (string, required): Exact package name (e.g. "express", "@types/node").

### `get_version_info` (~162 tokens)

Get metadata for a SPECIFIC version (or dist-tag) of an npm package: dependencies, dev/peer dependencies, engines, license, tarball + integrity hash + unpacked size, and any deprecation notice. Use for "dependencies of <pkg>@<version>", pinned-version audits, or inspecting a particular release. Version accepts an exact version (e.g. "4.18.2"), a dist-tag (e.g. "latest", "next"), or omit for the latest.

Input parameters:

- `name` (string, required): Exact package name (e.g. "express").
- `version` (string): Exact version (e.g. "4.18.2"), a dist-tag (e.g. "latest", "next"), or omit for latest.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-npm/pipeworx-mcp-npm#diagnostics

## Score history

- 2026-11-05: 85
- 2026-11-04: 85
- 2026-11-03: 69
- 2026-11-02: 84
- 2026-11-01: 83
- 2026-10-31: 83
- 2026-10-30: 82
- 2026-10-29: 82

## Common questions

### What is the Npm MCP server?

Npm is an MCP server listed in the public MCP registry as io.github.pipeworx-io/npm. npm MCP, wraps the npm Registry API (free, no auth). This page covers its npm package (@pipeworx/mcp-npm).

### Is the Npm MCP server safe to use?

Npm scores 85 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 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 Npm MCP server expose?

Npm exposes 5 tools: search_packages, get_package, get_downloads, list_versions, get_version_info. Their descriptions and schemas cost roughly 518 tokens of context every time the server is loaded.

### Is the Npm MCP server still maintained?

Npm is still listed as active in the MCP registry. We last reached this channel on 5 November 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 Npm MCP server under?

Npm 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 MCP server?

VerifyMCP ran 16 checks on Npm, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-npm
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-npm
- Repository: https://github.com/pipeworx-io/mcp-npm
- Website: https://pipeworx.io/packs/npm
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-npm/pipeworx-mcp-npm.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-npm/pipeworx-mcp-npm/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-npm/pipeworx-mcp-npm.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-npm/pipeworx-mcp-npm