Retrieve npm package metadata such as version, license, dependencies, and download statistics to verify package maintenance and assess risk before adding it as a dependency.
MIT
521,507 tools. Updated 2026-09-06 11:42
"npm" matching MCP tools:
- Retrieve TypeScript type definitions for specified NPM packages, sourced either from the main package or @types/. Supports version and search mode customization for precise type retrieval.-
- Analyze TypeScript type definitions for NPM packages to determine their status, recommend approaches, and suggest alternatives. Supports version-specific checks for improved development clarity.-
- Check for outdated npm packages in your project directory to identify dependencies needing updates.-
- Fix npm package vulnerabilities by running npm audit fix in a specified directory to address security issues in dependencies.-
- Get documentation for any npm package by discovering its GitHub repository and returning the README.md content.-
Matching MCP Servers
- AlicenseAqualityDmaintenanceModel Context Protocol server for npm registry. Enables searching packages, checking security, comparing versions, and validating compatibility.12573MIT
- AlicenseBqualityCmaintenanceMCP server for npm package management — publish, install, audit, search, security & dependency health38551MIT
Matching MCP Connectors
npm MCP — wraps the npm Registry API (free, no auth)
npm package trends and weekly downloads over time. Free key at trendsmcp.ai
- Return live npm registry facts for the latest or requested package version without the higher-priced vulnerability and adoption decision layer. Price: $0.01 via x402. _salt19_operation_id is recommended but optional for standard x402 compatibility.ConnectorNo auth
- Check whether an npm package is deprecated or vulnerable before installing it, including vulnerabilities, license, maintenance, freshness, dependency health, and package.json risk signals. Price: $0.05 via x402. Generate one _salt19_operation_id per intended purchase, preserve it across retries, and add _x402_payment_signature after satisfying the challenge. A stable _salt19_operation_id is required and makes semantic retries at-most-once. _salt19_operation_id is recommended but optional for standard x402 compatibility.ConnectorNo auth
- Check for outdated or insecure npm packages in an install script like `npm i` or `pnpm add` or `yarn add` or `bun i`.ConnectorNo auth
- x402-npm-audit: NPM package security audit. 🆓 5 free trial calls per registered walletConnectorNo auth
- Npm Package Info: Npm Package InfoConnectorNo auth
- Retrieve complete npm package details: versions, dependencies, maintainers, repository, license, size, npm score, and weekly downloads to evaluate package quality.MIT
- Assess npm package security risk for frontend projects. Get SHIP/CAUTION/BLOCK verdict, CVE counts, licence risk, maintainer health, weekly downloads, and UI component status.-
- Check installed package version against npm latest to receive safe update guidance without exposing credentials.Apache 2.0
- Install npm dependencies for a Varity project. Specify packages or run full install after project creation.MITDestructive
- Retrieve theme, Vite, and npm info for Pinoox single-app projects via the pinx fe:info command.MIT
- Check Composer and npm dependency status to identify outdated or missing packages.MIT
- Re-reads the npm token from ~/.npmrc, NPM_TOKEN, and config, and reports if it changed. Fixes 401s after terminal npm login without restarting.MIT
- Retrieve npm package metadata including version, documentation URLs, repository links, license, and maintainer information for informed development decisions.MIT
- Retrieve direct or transitive dependencies of an npm package. Returns summary counts, dependency lists by category, and an ASCII tree for production dependencies up to depth 5.MIT
- Check registry authentication status before troubleshooting missing tools. Reports token source, account, 2FA state, write permission, and cached OTP to identify configuration issues.MIT