Mmcp.market

pkgxray MCP server

by adamsjack711-ux·io.github.adamsjack711-ux/pkgxray·v1.0.5
No reviews yet

Pre-install security scans for npm packages, MCP servers, and AI agents with cited verdict evidence.

B74/100grade B
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
B74/100

full report

Adoption
Growing

11 stars38 downloads/wk

Reviews

Write one

Nobody has reviewed pkgxray yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

pkgxray tools

No tool declarations could be read from the package source. They show once the server is installed.

Public scan report

scanner v0.1.9 · 2026-09-24 · same rubric, same numbers if you re-run it

2 medium
  • Code scan23 source files scanned15/25
  • –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 0 days ago15/15
  • Maintainer identityregistry namespace matches repository owner6/10

Findings (2)

  • mediumeval / new Function usedexec.eval
    src/auditor.js: …`devtool:'eval'` wraps every module as `eval("<module source>")`, // and `new Functio…
  • mediumNetwork call to a raw IP addressnet.raw-ip
    src/auditor.js: …s not // execute: `// e.g. request.get('https://1.2.3.4/')` (superagent), an Apache // license U…
Overall 74/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

What the publisher says

From the pkgxray repository's README, as published. We do not edit it. Read it on GitHub

pkgxray — pre-install security for npm packages, MCP servers, and AI agents

Inspect an npm package or MCP server before you install it or connect to it. You get a SAFE, REVIEW, or BLOCK verdict, decided by fixed rules and backed by cited evidence. The analysis is static and runs on your machine without installing npm dependencies. A pinned MIT-licensed Acorn parser is bundled. Normal scans never execute package code.

Website · Documentation · Calibration · Report a bug

Real runs: guard clears express@4.21.0, then blocks a sample modeled on the 2024 @solana/web3.js compromise.

Highlights

  • No npm dependency installation — local Node analysis with a bundled, pinned JavaScript parser.
  • Install approved bytes — pkgxray install scans the npm lockfile, installs held archives offline with scripts disabled, and verifies the resulting files.
  • Normal scans never execute package code — the tarball is read as bytes in quarantine.
  • Cited verdicts from fixed rules — every finding names the file and the evidence. No model decides the verdict, so text planted in a package cannot steer it.
  • Built for the agent era — check MCP servers before you connect, gate the installs an agent runs, and re-audit live MCP traffic.
  • Adversarial gaps tracked openly — 200 additional synthetic cases track detected attacks and benign contrasts; this is internal testing, not an independent audit.
  • Regression gates — calibration and adversarial corpora run in CI; historical top-1000 results remain available for comparison.

1. Quick start · 2. What it scans & detects · 3. Verdicts · 4. Usage · 5. Integrations · 6. How it compares · 7. Documentation

Why

AI coding assistants install packages and connect to MCP servers quickly, and often no person reads the code first. Sonatype counted more than 454,600 new malicious open-source packages across monitored ecosystems in 2025, over 99% of them on npm (Sonatype). npm audit asks whether a package has a known CVE. pkgxray also asks what the code does, before anything installs.

Quick start

1. Scan a known-benign package (no install of pkgxray needed):

npx --yes pkgxray@1.0.5 guard npm:express@4.21.0

It stages the tarball in quarantine and runs the static and supply-chain checks. There is no npm install, no lifecycle script, and no package code executed.

Sample output

Decision: SAFE   Grade: A+ (99/100)
No high- or medium-risk indicators were found in the provided evidence.

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Install directly

Runs npx -y pkgxray on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add pkgxray -- npx -y pkgxray
Add to Cursor

pkgxray: common questions

Is pkgxray MCP server safe?
Mostly: it is graded B (74/100). Read the pkgxray safety report
How do I install pkgxray?
It runs on your machine. Copy the Claude Code, Claude Desktop or Cursor config from the install section.
Does pkgxray need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is pkgxray maintained?
The last commit was in the last day (2026-09-24). The latest release is v1.0.5.
What can I use instead of pkgxray?
Servers from other publishers that do the same job: npm Registry MCP Server, Npm Sentinel MCP server and Prodcheck MCP server. Compare all pkgxray alternatives.

Alternatives to pkgxray

Same job from other publishers: the closest match first, then the best rated.

All pkgxray alternatives →
  • npm Registry MCP Server
    npm registry MCP server — package intelligence, security audits, dependency analysis
    More from YawLabs →
    B
  • Npm Sentinel
    Advanced NPM analysis: Recursive security scanning, ecosystem awareness, and deep insights.
    A
  • Prodcheck
    4,372 pre-production checks: security, performance, scale, integrations, post-launch.
    A
  • MCP
    Security tools for your AI: scan, pentest, check headers, guard code and scan repos for secrets.
    A
  • SecHelix
    Evidence-first security review of authorized repositories. Read-only, root-confined, no shell.
    A
pkgxray vs npm Registry MCP Serverpkgxray vs Npm Sentinelpkgxray vs Prodcheck

More from adamsjack711-ux →