npm mcp

    1

    MCP server that reads package.json files and checks dependency ranges against the latest npm version.

    Free

    Security scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    npm mcp

    Example session with this skill installed

    Check the dependency freshness for the project located in the current directory and list any packages that are outside their declared range.

    • Read your context and instructions
    • Compiled the npm mcp

    I have analyzed the dependencies for the project in the current directory, including its workspaces. I checked the declared ranges against the latest versions on the npm registry.

    Dependency Freshness Report

    PathNameSourceRangeLatestStatus
    package.jsonlodashdependencies^4.17.204.17.21inside
    package.jsontypescriptdevDependencies^5.0.05.3.3inside
    package.jsonvitedevDependencies^4.0.05.1.4outside
    packages/client/package.jsonreactdependencies^18.2.018.2.0inside
    packages/server/package.jsonexpressdependencies~4.16.04.18.2outside
    packages/shared/package.jsonzoddependencies3.22.43.22.4inside

    Summary:

    • Inside range: 4 packages
    • Outside range: 2 packages (vite, express)
    • Unparsed/Missing: 0 packages

    Next steps

    1. Update vite in the root package.json to ^5.1.4 to align with the latest major release.
    2. Review the breaking changes for express before bumping the tilde range in packages/server/package.json.
    3. Run npm install to synchronize your lockfile with these findings.
    package.json

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Dependency drift happens fast. This skill automates the tedious task of auditing package.json files against the live npm registry so you stop shipping outdated or incompatible code.

    What it does

    • Manifest parsing reads root and workspace package.json files to extract scripts, licenses, and dependency sets.
    • Registry lookup fetches the latest published version and license data directly from registry.npmjs.org.
    • Workspace expansion resolves glob patterns in project workspaces to map out monorepo structures.
    • Freshness auditing compares declared semver ranges against registry truth to find versions falling outside of bounds.
    • Semver validation handles caret, tilde, and exact version logic to determine if the latest release satisfies your constraints.

    How it works

    1. Point the tool at a project directory to discover all manifests.
    2. Run a freshness check to compare dependencies, devDependencies, and peerDependencies.
    3. Review the status table to see which packages are inside or outside their ranges.
    4. Query specific package info for individual registry details.

    Frameworks & tools

    Built for Node.js and npm ecosystems. Works with monorepo workspaces and projects using standard semver. The server is implemented in Go and communicates via the Model Context Protocol (MCP).

    Why this beats prompting it yourself

    Manual version checking is slow and error-prone. This skill has direct access to the npm registry API and native semver logic, allowing it to accurately verify hundreds of dependencies in seconds without you leaving your editor.

    Use cases

    • Audit a legacy project to find critical dependency lag.
    • Validate monorepo workspaces and shared dependency ranges.
    • Check if "latest" releases still fit within your existing ^ or ~ bounds.
    • Extract project metadata and scripts for documentation or CI analysis.

    Known limitations

    Does not support complex semver operators like ||, prerelease versions, or git/URL specs. Requires Go 1.27+ to build the binary. Registry failures other than 404 will stop the execution.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for LLM Ops.

    Requires Go 1.27+ for building. Skips complex ranges (||, x-ranges, git/URL specs). Registry License objects for specific packages may cause lookup failure.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Free to use

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 9 days ago

    • Free with an Agensi account

    Software
    Npm MCP

    Permissions

    Terminal / Shell
    Read Files
    Write Files
    Network Access
    Listed9 days ago

    What's inside

    Frequently Asked Questions

    This skill provides the AI with direct, programmatic access to the npm registry and your local file system, allowing it to perform precise semver audits and monorepo mapping that a standard LLM cannot do accurately by memory alone.

    It is compatible with any AI agent or IDE that supports the Model Context Protocol (MCP), such as Claude Desktop or Cursor, and requires a Go 1.27+ environment to build the binary.

    Yes, the tool is specifically designed to handle workspace expansion, resolving glob patterns to audit all package.json files across a monorepo structure simultaneously.

    The server handles standard caret (^), tilde (~), and exact versioning; however, it does not currently support complex logical operators like OR (||), git URLs, or prerelease tags.

    The tool performs a 'freshness audit' by fetching the latest registry data and comparing it against your declared ranges, flagging any packages where the newest version has drifted outside your specified constraints.

    New in LLM Ops

    Free