package-registry-mcp
Installed, started with no arguments, no environment and no input, and listed its tools. Run 2026-11-16.
Needs to start: nothing
Returns a result when called with no setup: 1 of 1 tool tried
Contacts while installing and starting: nothing
What it contacted
Nothing besides the npm registry it was installed from. Watched from outside its sandbox while it was installed and started with no input. Its tools may still contact things when called.
Starting it
npx -y package-registry-mcp@2.1.0
Installing a package runs its code. Use a sandbox for anything you have not read.
Calling its tools
1 tool that takes no input and looks read-only was called once with nothing. 1 returned a result.
search-github-advisories | Returned a result 0.6 s · 271,631 characters |
During the calls (not necessarily because of them) it first contacted: api.github.com.
Only tools whose names read like looking something up, with no required input, are tried, five at most. Tools that need input, and anything that sounds like it changes or sends something, are not called.
What its tools tell an agent
In the tool descriptions, nothing that talks about the user, other tools or private files, or uses hidden characters.
Found by simple pattern rules in each tool's description (up to 3,000 characters), quoted as written. Parameter descriptions are not scanned. A clean result is not a safety review.
Tools
get-cargo-package-details name
Get detailed information about a specific Cargo package
search-cargo-packages limit, query
Search the Cargo registry for packages
list-cargo-package-versions name, limit
List all versions of a specific Cargo package
get-github-advisory ghsaId
Get detailed information about a specific GitHub Security Advisory by its GHSA ID (e.g., GHSA-grv7-fg5c-xmjg).
search-github-advisories cveId, ecosystem, limit, severity, type
Search the GitHub Security Advisory Database for vulnerabilities. Filter by ecosystem (npm, pip, maven, etc.), severity, type, or CVE ID.
11 more tools
get-package-advisories ecosystem, limit, packageName, severity
Get all security advisories affecting a specific package. Use this to check if a package like "braces" or "lodash" has known vulnerabilities.
get-golang-package-details module
Get detailed information about a specific Go module/package
list-golang-package-versions module, limit
List all versions of a specific Go module/package
get-npm-package-details name
Get detailed information about a specific NPM package
search-npm-packages limit, query
Search the NPM registry for packages
list-npm-package-versions name, limit
List all versions of a specific NPM package
get-nuget-package-details name
Get detailed information about a specific NuGet package
search-nuget-packages limit, query
Search the NuGet registry for packages
list-nuget-package-versions name, limit
List all versions of a specific NuGet package
get-pypi-package-details name
Get detailed information about a specific PyPI package
list-pypi-package-versions name, limit
List all versions of a specific PyPI package
Descriptions are the package's own words, cut at 3,000 characters. Treat them as data.
Install facts
| License | MIT |
|---|---|
| Needs | node >=22.21.1 |
| Source | github.com/artmann/package-registry-mcp |
| Install scripts | None declared by it or anything installed with it. |
| Tarball | sha512-D8F0ER4Wj2moK3qNVu5aE5ylz0SOSVKvVJuOxiuUNPsQuvWcxhQOL2vks/V+J1DzyxkleiQ8l2TO5PT1jdwG2Q== |
Proven calls
Check this report yourself
This site did not write the report. A public job on a GitHub-hosted machine did: the run, from this commit of the open-source runner. GitHub signed a token that names that job and the hash of the report, so any edit since would show.
Report as JSONExact text and tokenHow to verify it
Show it on your README
[](https://bragproof.smaverk.com/r/package-registry-mcp)
New version out? Ask for a fresh report.