npmguard
Related Servers
Alternatives to npmguard
- AlicenseAqualityDmaintenanceMCP server to search npm packages, view details, compare, check downloads, and inspect dependencies.621MIT
Related Servers
- AlicenseNot gradedqualityCmaintenanceAudits npm packages for supply-chain attacks (typosquatting, malicious install scripts, credential exfiltration) before installation, returning a SAFE/SUSPICIOUS/DANGEROUS verdict.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to automatically verify npm packages against the live registry before installation, flagging hallucinated, slopsquatted, or otherwise suspicious packages with risk verdicts.0MIT
- AlicenseAqualityCmaintenanceVerifies npm packages for security risks before installation, checking advisories, install scripts, typosquatting, and other factors, providing safe/block verdicts.1Apache 2.0
- AlicenseAqualityAmaintenanceEnables AI coding agents and CI to vet npm dependencies before they reach the lockfile, flagging hallucinated, slopsquatted, or otherwise risky packages with evidence-backed verdicts.34933MIT
- AlicenseNot gradedqualityDmaintenanceAudits your package-lock.json for supply-chain attacks before install. Cross-checks every resolved entry against the live npm registry to detect integrity mismatches, new install scripts, and other malicious signals.MIT
- AlicenseNot gradedqualityCmaintenanceScans generated JavaScript/TypeScript code to detect AI-hallucinated or suspicious npm package imports before installation, providing a verdict of CLEAN, REVIEW, or BLOCK.41MIT
TDQS
Scored across 1 tool
There is only one tool, so there is zero possibility of selecting the wrong tool. Its purpose is clearly defined and distinct from any nonexistent alternatives.
The single tool name 'install_package' follows a clean verb_noun pattern. Although the name implies installation rather than evaluation, it is consistent and predictable within this one-tool set.
The server has just one tool, which feels thin for a typical server and borders on the minimum viable scope. While the tool covers a specific need, it does not reach the 3-15 tool range that indicates a well-populated set.
For the stated purpose of evaluating npm package risk, the tool fully covers the single required action. Minor gaps include lack of support for batch evaluation or detailed policy management, but the core lifecycle of 'check before install' is complete.