npm Registry API
npm Registry API for searching JavaScript packages and retrieving package metadata, versions, distribution tags, and published manifests.
Connect this API to an AI agent Browse all specs
What you can do with npm Registry API via MCP
Every endpoint below becomes a governed tool your AI agent (Claude, ChatGPT, or a customer-facing VX agent) can call — with scoped permissions, sandbox testing, and audit logs.
| Method | Path | Operation | Description |
|---|---|---|---|
| GET | /-/v1/search |
get_v1_search | Search npm packages Method: GET Path: /-/v1/search IMPORTANT: This function has 1 REQUIRED parameter(s) and 2 OPTIONAL parameter(s) REQUIRED parameters MUST be provided OPTIONAL parameters can be omitted if not needed Parameters: Query Parameters: REQUIRED: - text: Search terms OPTIONAL: - size: Number of results - from: Offset into results |
| GET | /{package} |
get_package | Get package metadata Method: GET Path: /{package} IMPORTANT: This function has 1 REQUIRED parameter(s) and 0 OPTIONAL parameter(s) REQUIRED parameters MUST be provided OPTIONAL parameters can be omitted if not needed Parameters: Path Parameters: REQUIRED: - package: URL-encoded package name, including scoped names |
| GET | /{package}/{version} |
get_package_version | Get a specific package version Method: GET Path: /{package}/{version} IMPORTANT: This function has 2 REQUIRED parameter(s) and 0 OPTIONAL parameter(s) REQUIRED parameters MUST be provided OPTIONAL parameters can be omitted if not needed Parameters: Path Parameters: REQUIRED: - package: URL-encoded package name - version: Semver version or dist-tag |
| GET | /-/package/{package}/dist-tags |
get_package_package_dist_tags | Get package distribution tags Method: GET Path: /-/package/{package}/dist-tags IMPORTANT: This function has 1 REQUIRED parameter(s) and 0 OPTIONAL parameter(s) REQUIRED parameters MUST be provided OPTIONAL parameters can be omitted if not needed Parameters: Path Parameters: REQUIRED: - package: URL-encoded package name |
Usage guide
Public package discovery and metadata routes do not require an API key or bearer token. Use a descriptive `User-Agent`, respect registry rate limits, and use npm credentials only for private or publishing operations that are outside this read-focused specification. Official documentation: https://github.com/npm/registry/blob/main/docs/REGISTRY-API.md
How to use this spec
- Create a free VX Agents account (sandbox tools included).
- Open the marketplace and connect “npm Registry API” to an agent.
- Expose it as an MCP server for Claude/ChatGPT, or chat with it directly.