Pkgverdict MCP server
by CloudCorpRecords·
io.github.CloudCorpRecords/pkgverdict·v0.1.1Pre-install verdicts for npm packages: GO, RISKY, FAKE, or MISSING. Built for humans and AI agents.
A88/100grade A
Adoption
New
0 stars
Reviews
Write oneNobody has reviewed Pkgverdict yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Pkgverdict tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.10 · 2026-10-24 · same rubric, same numbers if you re-run it
no findings
- –Code scanpackage could not be scannedn/a
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 1 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 88/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON
How Pkgverdict compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 88/100
- higher than 75% of 48,273 servers
Install Pkgverdict in Claude Code, Cursor or VS Code
claude mcp add pkgverdict -- docker run -i --rm ghcr.io/cloudcorprecords/pkgverdict:0.1.1
Pkgverdict: common questions
- Is Pkgverdict MCP server safe?
- Yes, by our scan: it is graded A (88/100). Read the Pkgverdict safety report
- How do I install Pkgverdict?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Pkgverdict need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Pkgverdict maintained?
- The last commit was 10 days ago (2026-10-23). The latest release is v0.1.1.