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.

io.github.Dave-London/npm

NPM · @PARETOOLS/NPM · SCANNED SEP 20

Structured npm/pnpm operations (install, audit, outdated, list) as typed JSON.

Available components

0 this week 96 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
  • 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to Dave-London/Pare). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 31 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability81
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 794 tokens (~88/item across 9 items; 9 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
  • Stability observed for 29 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
  • 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 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 10 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 io.github.Dave-London/npm MCP server?

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

npm · @paretools/npm

# add to Claude Code
claude mcp add dave-london-npm -- npx -y @paretools/npm
// .cursor/mcp.json
{
  "mcpServers": {
    "dave-london-npm": {
      "command": "npx",
      "args": [
        "-y",
        "@paretools/npm"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "dave-london-npm": {
      "command": "npx",
      "args": [
        "-y",
        "@paretools/npm"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add dave-london-npm -- npx -y @paretools/npm
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dave-london-npm": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@paretools/npm"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add dave-london-npm --command npx --arg -y --arg @paretools/npm
# ~/.hermes/config.yaml
mcp_servers:
  dave-london-npm:
    command: "npx"
    args: ["-y", "@paretools/npm"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "dave-london-npm": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@paretools/npm"
      ]
    }
  }
}
# add to Vellum
assistant mcp add dave-london-npm -t stdio -c npx -a -y @paretools/npm
// mcp.json
{
  "mcpServers": {
    "dave-london-npm": {
      "command": "npx",
      "args": [
        "-y",
        "@paretools/npm"
      ]
    }
  }
}
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 +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.

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

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

  • 15 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 14 Sept 26 0
    • Stability: 0.97 → pass security
  • 13 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.

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

  • 9 Sept 26 −2
    • Stability: pass → 0.83 functional
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/@paretools/npm@0.8.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 Dave-London/Pare
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/Dave-London/Pare/.github/workflows/release.yml@refs/heads/main
Rekor log index 949168400
Predicate type https://slsa.dev/provenance/v1
Subject digest sha512:0dfa0039e147ebc20362e23cf766092154be570445a2951a6b6159f4959c7ed2b8d11416dc57e45be68282eeba123c4996c4d939e359fa7c4617185ac

Background: How many MCP packages publish verified provenance →

Dependencies 96 packages
Packages resolved 96
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 9 exposed · ~748 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
audit ~42

Runs npm audit and returns structured vulnerability data. Use instead of running `npm audit` in the terminal.

NameTypeReqDescription
pathstringProject root path (default: cwd)
NameTypeReqDescription
summaryobjectyes
vulnerabilitiesarrayyes

No examples provided.

info ~94

Shows detailed package metadata from the npm registry. Use instead of running `npm info` in the terminal.

NameTypeReqDescription
compactbooleanAuto-compact when structured output exceeds raw CLI tokens. Set false to always get full schema.
packagestringyesPackage name to look up (e.g. 'express', 'lodash@4.17.21')
pathstringProject root path (default: cwd)
NameTypeReqDescription
dependenciesobject
descriptionstringyes
distobject
homepagestring
licensestring
namestringyes
versionstringyes

No examples provided.

init ~85

Initializes a new package.json in the target directory. Returns structured output with the package name, version, and path.

NameTypeReqDescription
pathstringDirectory to initialize (default: cwd)
scopestringnpm scope for the package (e.g., '@myorg')
yesbooleanUse -y flag for non-interactive init with defaults (default: true)
NameTypeReqDescription
packageNamestringyesThe name field from the generated package.json
pathstringyesPath to the generated package.json
successbooleanyesWhether package.json was created successfully
versionstringyesThe version field from the generated package.json

No examples provided.

install ~145

Runs npm install and returns a structured summary of added/removed packages and vulnerabilities. Use instead of running `npm install` in the terminal. Lifecycle scripts (preinstall/postinstall) are skipped by default for safety. Set ignoreScripts to false if packages need postinstall scripts to work (e.g., esbuild, sharp).

NameTypeReqDescription
argsarrayAdditional arguments (e.g., package names to install)
ignoreScriptsbooleanSkip lifecycle scripts (preinstall/postinstall). Defaults to true for safety. Set to false if packages need postinstall scripts to run (e.g., esbuild, sharp).
pathstringProject root path (default: cwd)
NameTypeReqDescription
addednumberyes
changednumberyes
durationnumberyes
fundingnumber
packagesnumberyesTotal packages after install
removednumberyes
vulnerabilitiesobject

No examples provided.

list ~85

Lists installed packages as structured dependency data. Use instead of running `npm list` in the terminal.

NameTypeReqDescription
compactbooleanAuto-compact when structured output exceeds raw CLI tokens. Set false to always get full schema.
depthnumberDependency tree depth (default: 0, top-level only)
pathstringProject root path (default: cwd)
NameTypeReqDescription
dependenciesobjectyes
namestringyes
totalnumberyes
versionstringyes

No examples provided.

outdated ~43

Checks for outdated packages and returns structured update information. Use instead of running `npm outdated` in the terminal.

NameTypeReqDescription
pathstringProject root path (default: cwd)
NameTypeReqDescription
packagesarrayyes
totalnumberyes

No examples provided.

run ~89

Runs a package.json script via `npm run <script>` and returns structured output with exit code, stdout, stderr, and duration. Use instead of running `npm run` in the terminal.

NameTypeReqDescription
argsarrayAdditional arguments passed after -- to the script
pathstringProject root path (default: cwd)
scriptstringyesThe package.json script name to run
NameTypeReqDescription
durationnumberyesExecution duration in seconds
exitCodenumberyesProcess exit code (0 = success)
scriptstringyesThe script that was executed
stderrstringyesStandard error from the script
stdoutstringyesStandard output from the script
successbooleanyesWhether the script exited with code 0

No examples provided.

search ~96

Searches the npm registry for packages matching a query. Use instead of running `npm search` in the terminal.

NameTypeReqDescription
compactbooleanAuto-compact when structured output exceeds raw CLI tokens. Set false to always get full schema.
limitnumberMaximum number of results to return (default: 20)
pathstringProject root path (default: cwd)
querystringyesSearch query string
NameTypeReqDescription
packagesarrayyes
totalnumberyes

No examples provided.

test ~69

Runs `npm test` and returns structured output with exit code, stdout, stderr, and duration. Shorthand for running the test script defined in package.json.

NameTypeReqDescription
argsarrayAdditional arguments passed after -- to the test script
pathstringProject root path (default: cwd)
NameTypeReqDescription
durationnumberyesExecution duration in seconds
exitCodenumberyesProcess exit code (0 = success)
stderrstringyesStandard error from the test run
stdoutstringyesStandard output from the test run
successbooleanyesWhether tests passed (exit code 0)

No examples provided.

Common questions

What is the io.github.Dave-London/npm MCP server?

io.github.Dave-London/npm is an MCP server listed in the public MCP registry as io.github.Dave-London/npm. Structured npm/pnpm operations (install, audit, outdated, list) as typed JSON. This page covers its npm package (@paretools/npm).

Is the io.github.Dave-London/npm MCP server safe to use?

io.github.Dave-London/npm scores 96 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 io.github.Dave-London/npm MCP server expose?

io.github.Dave-London/npm exposes 9 tools: install, audit, outdated, list, run, and 4 more. Their descriptions and schemas cost roughly 748 tokens of context every time the server is loaded.

Is the io.github.Dave-London/npm MCP server still maintained?

io.github.Dave-London/npm 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 io.github.Dave-London/npm MCP server under?

io.github.Dave-London/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.