check_package
Check if a specific npm package is deprecated
How to use it
check_package is exposed by the Npm Deprecated Check MCP server. Add the server to your MCP client (Claude Desktop, Cursor, Windsurf and others), and the check_package 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 --mcpOther tools in Npm Deprecated Check (12)
Check Node.js version compatibility for a project or package
Check all dependencies of the current project
Check globally installed packages
Check if the current Node.js version has reached EOL
(optional) — deep inspection for monorepo projects
(optional) — comma-separated package names to ignore
(optional) — package manager: "npm", "yarn", or "pnpm" (default: "npm")
(optional) — target Node.js version (e.g. "18", "20.11.0"). Defaults to current Node version
(required) — npm package name
(optional) — absolute path to project root (only used when packageName is not provided)
(optional) — version range, e.g. "^1.0.0"
(optional) — custom npm registry URL