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.
Warning

Malware flagged

A supply-chain scanner flagged a high-severity malware risk in this package. Treat it as unsafe to install until the finding is cleared. See Supply Chain Security in the trust breakdown.

io.github.Baneado98/npm-guardian

NPM · NPM-GUARDIAN-MCP · SCANNED AUG 5

npm supply-chain audit: known CVEs (OSV), typosquatting, malicious scripts — before npm install.

Available components

0 Trust /100

Deleted

This server was marked deleted in the MCP registry on 2026-08-04 20:55:13.005171+00. Its details are retained for reference.

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 Security41
  • Malware check failed: a supply-chain vendor flagged a high-severity malware risk. See how to fix → Fail
  • Known CVEs were checked across the 94 of 98 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
  • No install/post-install scripts declared.Pass
  • Dependency health was assessed across the 94 of 98 dependencies we could resolve, so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency19
  • Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
  • 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 42 days ago).Pass
  • Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability77
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 285 tokens (~142/item across 2 items; 2 tools + 0 resources), lean.Pass
  • 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
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 1 category

A category scored 0 because we could not verify it: 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.

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 · npm-guardian-mcp

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

  • 5 Aug 26 −16
    • Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
    • Tool coverage: unverified → 100 functional
    • MCP protocol: unverified → pass functional
    • First check of Schema quality: fail functional
    • First check of Schema quality: excellent functional
    • First check of Schema quality: pass functional
    • First check of Tool coverage: 100 functional
  • 4 Aug 26 16

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

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm
Dependencies 94 packages
Packages resolved 94
Deprecated 94
Stale 29
Tree resolution Partial

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

MCP tools — 2 exposed · ~285 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
audit_many ~52

Audit several npm packages at once (e.g. an entire dependency list). Returns one verdict per package. Useful to vet a package.json before installing.

NameTypeReqDescription
namesarrayyesList of npm package names to audit.

No output schema declared.

No examples provided.

audit_npm_package ~233

Run a supply-chain security audit on an npm package BEFORE installing it. Cross-references the exact version against published CVE/GHSA vulnerability advisories (via OSV.dev) and tells you the fixed version to upgrade to, AND detects typosquatting, malicious install/postinstall scripts, credential & crypto-key exfiltration markers, freshly-published low-trust packages and missing source repos. Returns a SAFE / SUSPICIOUS / DANGEROUS verdict with a risk score and explained findings. Use this whenever you are about to run 'npm install <pkg>' or add a dependency you are not 100% sure about.

NameTypeReqDescription
deepbooleanWhen true, also downloads and statically inspects the REAL published tarball (source files + index/tarball tampering), not just registry metadata. Slower but catches payloads hidden in source. Recomm…
namestringyesThe npm package name, e.g. 'lodash' or '@scope/pkg'.
versionstringOptional specific version to audit. Defaults to latest.

No output schema declared.

No examples provided.