get-cargo-package-details
Get detailed information about a specific Cargo package
LABSCO SUMMARY
Version lookup and vulnerability lookup answered by one server, so an upgrade is one conversation.
The per-registry tools are uniform — details, versions, and search where it exists — and the advisory tools take an ecosystem argument naming those same registries, so "is there a newer version, and does the one we ship have a CVE" is two calls in the same place. Coverage is not symmetric: Cargo, npm and NuGet have search tools, while Go and PyPI are addressed by exact name or module path.
What it is
A lookup server over five package registries and the GitHub Security Advisory Database, with the same ecosystem names running through both halves.
What you get
- Package details and full version lists for Cargo, npm, NuGet and PyPI
- Go module details and version lists, addressed by module path
- Registry search by query for Cargo, npm and NuGet
- get-package-advisories, which returns every advisory affecting one named package, filtered by ecosystem and severity
- The advisory database searched by ecosystem, severity, type or CVE ID, and one advisory fetched by its GHSA ID
Requirements
Nothing — no account, no key.
Setup effort
One command — npx package-registry-mcp
USE CASES
01
Choosing between two packages that claim the same thing
Search the registry with a limit, pull the details for the shortlist, and read the version list to see how the release history actually looks before either name goes into the project.
02
Vetting a dependency before it reaches the lockfile
Ask for every advisory affecting the package by name, widen to an ecosystem-and-severity search when the question runs broader than the one package, and pull the full record by GHSA id for anything that needs reading in detail.
03
Pinning versions across a repo that speaks four languages
Each registry has its own version-list tool taking the same shape of argument, so the current and previous versions of a Cargo crate, a PyPI package, a Go module and a NuGet package can be gathered in one pass.
16 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
get-github-advisory
Get detailed information about a specific GitHub Security Advisory by its GHSA ID (e.g., GHSA-grv7-fg5c-xmjg).
get-golang-package-details
Get detailed information about a specific Go module/package
get-npm-package-details
Get detailed information about a specific NPM package
get-nuget-package-details
Get detailed information about a specific NuGet package
get-package-advisories
Get all security advisories affecting a specific package. Use this to check if a package like "braces" or "lodash" has known vulnerabilities.
get-pypi-package-details
Get detailed information about a specific PyPI package
list-cargo-package-versions
List all versions of a specific Cargo package
list-golang-package-versions
List all versions of a specific Go module/package
list-npm-package-versions
List all versions of a specific NPM package
list-nuget-package-versions
List all versions of a specific NuGet package
list-pypi-package-versions
List all versions of a specific PyPI package
search-cargo-packages
Search the Cargo registry for packages
search-github-advisories
Search the GitHub Security Advisory Database for vulnerabilities. Filter by ecosystem (npm, pip, maven, etc.), severity, type, or CVE ID.
search-npm-packages
Search the NPM registry for packages
search-nuget-packages
Search the NuGet registry for packages
BEFORE YOU INSTALL
What to know first
Tools you get
16 tools when we connected. NPM, crates.io and NuGet get search, details and versions; PyPI and Go get details and versions only. Nothing installs or changes a project.
Requires
- Node.js 18+ or Bun runtime
- Internet connection for package registry access
CONTEXT COST
Light Standing cost
Rated by the size of the 16 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npx package-registry-mcpMCP Clients
Cursor, Claude Desktop
JSON
{
"mcpServers": {
"package-registry": {
"command": "npx",
"args": [
"package-registry-mcp"
]
}
}
}Claude Code
CLAUDE CODE · TERMINAL
claude mcp add -s user package-registry npx package-registry-mcp
