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
304,864 tools. Last updated 2026-07-21 16:13
"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.
- Compare npm package download trends for up to 5 packages. Returns total downloads and week-over-week trend for the requested period (last-week, last-month, last-year). Useful for evaluating package adoption before adding a dependency, comparing competing libraries (express vs fastify, react-query vs tanstack-query), or tracking whether a package is growing or declining. Free upstream: api.npmjs.org (no key required).Connector
Matching MCP Servers
- AlicenseBqualityCmaintenanceMCP server for npm package management — publish, install, audit, search, security & dependency healthLast updated38731MIT
- Alicense-qualityCmaintenanceAudits npm packages for supply-chain attacks (typosquatting, malicious install scripts, credential exfiltration) before installation, returning a SAFE/SUSPICIOUS/DANGEROUS verdict.Last updatedMIT
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
- Node.js / JavaScript package metadata from the npm registry. Returns latest version, description, license, keywords, direct dependencies, weekly download count, publish date, GitHub repository, and all recent versions. Also supports looking up a specific version. Use before adding an npm package as a dependency: verify it's maintained, check its license, assess how many dependencies it pulls in. Free upstream: npm registry API (no key, public).Connector
- Check for outdated or insecure npm packages in an install script like `npm i` or `pnpm add` or `yarn add` or `bun i`.Connector
- Assess npm package security risk with frontend-specific signals: weekly downloads, UI component flag, CVE counts, licence risk, and maintainer health. Returns SHIP/CAUTION/BLOCK verdict.Sleepycat
- Publish an npm package by bumping version, packing, and pushing to registry, gated by security audit and founder approval. Dry-run available for testing the chain without publishing.MIT
- Compare npm packages side-by-side by downloads, bundle size, dependencies, GitHub stars, and exported APIs to choose between alternatives.MIT
- Install npm dependencies for a Varity project. Specify packages or run full install after project creation.MIT
- Retrieve version details, available versions, and breaking changes for any npm package by specifying the package name and optional version range.MIT
- Retrieve the latest version and changelog for npm packages. Input package names to get current release information.MIT
- Retrieve all available versions of specified npm packages. Use to check version history or manage dependencies.MIT
- Retrieve the README content for NPM packages, enabling direct access to package documentation for analysis or review.MIT
- Retrieve maintainer details for NPM packages to verify package ownership and maintainer trust.MIT
- Retrieve theme, Vite, and npm info for Pinoox single-app projects via the pinx fe:info command.MIT
- Scan project dependencies to detect license compliance issues, including copyleft conflicts and proprietary risks. Supports npm and Python projects.MIT
- Check Composer and npm dependency status to identify outdated or missing packages.MIT