MCPVault

nodeVersion

MCP tool from Npm Deprecated Check by KID-joker

(optional) — target Node.js version (e.g. "18", "20.11.0"). Defaults to current Node version

How to use it

nodeVersion is exposed by the Npm Deprecated Check MCP server. Add the server to your MCP client (Claude Desktop, Cursor, Windsurf and others), and the nodeVersion tool becomes available to the model automatically. See the full listing for setup details and every tool this server provides.

Install Npm Deprecated Check

$npx -y npm-deprecated-check --mcp
FULL NPM DEPRECATED CHECK LISTING

Other tools in Npm Deprecated Check (12)

check_compat

Check Node.js version compatibility for a project or package

check_current_project

Check all dependencies of the current project

check_global

Check globally installed packages

check_node

Check if the current Node.js version has reached EOL

check_package

Check if a specific npm package is deprecated

deep

(optional) — deep inspection for monorepo projects

ignore

(optional) — comma-separated package names to ignore

manager

(optional) — package manager: "npm", "yarn", or "pnpm" (default: "npm")

packageName

(required) — npm package name

projectPath

(optional) — absolute path to project root (only used when packageName is not provided)

range

(optional) — version range, e.g. "^1.0.0"

registry

(optional) — custom npm registry URL