get_package_version — NPMScan MCP Tool Read-only
get_package_version
(get package version) is one of 23 tools on the
NPMScan
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_package_version from your client
- Claude Code NPMScan get_package_version run in your project directory
- Claude Desktop NPMScan get_package_version ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor NPMScan get_package_version ~/.cursor/mcp.json
- VS Code NPMScan get_package_version .vscode/mcp.json
- Zed NPMScan get_package_version ~/.config/zed/settings.json
- Windsurf NPMScan get_package_version ~/.codeium/windsurf/mcp_config.json
- Cline NPMScan get_package_version ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI NPMScan get_package_version ~/.gemini/settings.json
- Grok NPMScan get_package_version .mcp.json (in your project root)
- ChatGPT NPMScan get_package_version Settings → Connectors → Advanced → Developer mode
- Claude.ai NPMScan get_package_version Settings → Connectors → Add custom connector
- LangChain NPMScan get_package_version pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http npmscan https://npmscan.com/api/mcpOther tools on this server
- search_packages
- get_package
- get_maintainer_profile
- query_vulnerabilities
- batch_query_vulnerabilities
- get_latest_advisories
- get_cve
- analyze_install_script
- analyze_transitive_dependencies
- check_package_provenance
- check_maintainer_changes
- check_maintainer_blast_radius
- check_license_compliance
- diff_dependencies
- prioritize_remediation
- simulate_dependency_upgrade
- suggest_alternative
- compare_packages
- audit_github_repository
- get_remediation_playbook
- generate_sbom
- enrich_npm_audit
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.