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
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, and this page is not indexed.
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 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
Tool Safety–
Not scored yet: our latest scan of this package recorded no findings here. That is usually because the category is newer than the scan, or because we have not captured the MCP schema this package serves yet. It fills in the next time we score it.
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.
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.
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/npm-guardian-mcp@0.3.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
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.
Background: SBOMs and build attestations, explained →
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 →
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.
| Name | Type | Req | Description |
|---|---|---|---|
| names | array | yes | List 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.
| Name | Type | Req | Description |
|---|---|---|---|
| deep | boolean | – | When 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… |
| name | string | yes | The npm package name, e.g. 'lodash' or '@scope/pkg'. |
| version | string | – | Optional specific version to audit. Defaults to latest. |
No output schema declared.
No examples provided.
What is the io.github.Baneado98/npm-guardian MCP server?
io.github.Baneado98/npm-guardian is an MCP server listed in the public MCP registry as io.github.Baneado98/npm-guardian. npm supply-chain audit: known CVEs (OSV), typosquatting, malicious scripts, before npm install. This page covers its npm package (npm-guardian-mcp).
Is the io.github.Baneado98/npm-guardian MCP server safe to use?
io.github.Baneado98/npm-guardian scores 0 out of 100 on VerifyMCP. A supply-chain scanner flagged a possible malware risk on one channel of this server. It declares no install or post-install scripts. 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.Baneado98/npm-guardian MCP server expose?
io.github.Baneado98/npm-guardian exposes 2 tools: audit_npm_package, audit_many. Their descriptions and schemas cost roughly 285 tokens of context every time the server is loaded.
Is the io.github.Baneado98/npm-guardian MCP server still maintained?
io.github.Baneado98/npm-guardian has been deleted from the MCP registry. 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.Baneado98/npm-guardian MCP server under?
io.github.Baneado98/npm-guardian declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.