Log inSubmit server
Pkgxray logo

Pkgxray

Static-scans packages, MCP servers, and agent extensions before installation or connection, returning cited SAFE, REVIEW, or BLOCK verdicts.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Pkgxray

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "pkgxray": {
      "command": "npx",
      "args": [
        "--yes",
        "pkgxray@1.0.5"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

We couldn’t confirm it starts correctly

We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

npx --yes pkgxray@1.0.5

No response to initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 1mo ago.

Overview

The pkgxray MCP server exposes pkgxray's package-auditing capabilities to MCP clients and agents. It performs local, static analysis of npm, PyPI, GitHub, lockfile, MCP-server, and agent-extension targets without executing package code during normal scans. Fixed rules produce cited SAFE, REVIEW, or BLOCK results with stable exit codes for automation. Reach for it when an agent or CI workflow needs to vet dependencies or MCP servers before installation or connection.

Use cases

  • Vet npm packages before an agent installs them
  • Scan PyPI dependencies in CI
  • Check an MCP server before connecting
  • Recheck lockfiles for dependency regressions
  • Gate package installations with cited findings

Key features

  • Static quarantined package analysis
  • SAFE, REVIEW, and BLOCK verdicts
  • Cited file-level evidence
  • npm and PyPI dependency auditing
  • MCP server pre-connection checks
  • Stable CI exit codes

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 3d ago

Recent health check succeeded.

11/15 checks healthy over the last 91d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 2d ago via OSV.dev · pkgxray@1.0.5 (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars12Stargazers on the source repository.
Last commit25d agoMost recent push to the default branch.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.
Directory activity6 viewsConfig copies, upvotes, and views on AllMCPs.

How Pkgxray works

What the pkgxray MCP server does

The pkgxray MCP server makes pkgxray's auditing functions available through MCP so an agent can use the same checks that are available from the command line. The project is designed to inspect software before installation, package promotion, or connection to an MCP server. It covers npm and PyPI packages, GitHub repositories, local directories, dependency lockfiles, MCP servers, and AI-agent extensions.

Results use three policy-oriented decisions. SAFE means no high- or medium-risk indicators were found and has exit code 0. REVIEW indicates incomplete evidence or a privileged capability requiring human inspection and has exit code 3. BLOCK indicates high-severity cited evidence and has exit code 2. Findings identify the relevant file and evidence rather than returning an unexplained score.

How it works

Normal scans stage package archives in quarantine and read them as bytes. Package code, lifecycle scripts, and install hooks are not executed during these scans. The verdict comes from fixed detection rules rather than a language model, so text inside a package cannot alter the decision logic.

Checks include credential and secret-store access, cloud metadata harvesting, prompt injection, Unicode smuggling, encoded payloads, stage-two loaders, exfiltration, persistence, CI/CD workflow injection, self-deleting droppers, registry replication, install-time execution, obfuscated command arguments, unpublished lockfile names, known CVEs, npm-to-GitHub artifact differences, trojaned updates, and suspicious MCP capability surfaces.

The guard command vets an individual target, audit examines supported dependency files, and recheck compares dependencies over time for regressions. The mcp command can gate an MCP server before connection and supports rechecking for changes. A runtime proxy mode can inspect each live MCP tool call, but that is a separate execution surface from ordinary static scanning.

Setup and configuration

The package is published on npm. The README demonstrates running a scan without first installing pkgxray locally:

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

A .pkgxray.json file can tune policy across entry points; when no configuration is present, the strictest settings apply. Configuration cannot suppress a CVE, and a scan error fails closed to REVIEW.

Tools and capabilities

The pkgxray MCP server is suited to exposing audit operations to coding agents and MCP clients. The underlying command-line surfaces support:

  • Pre-install checks for npm and PyPI packages.
  • Scans of GitHub repositories and local directories.
  • Audits for npm and Python dependency manifests and lockfiles.
  • Pre-connection checks for MCP servers.
  • Scheduled dependency rechecks for upgrade regressions.
  • JSON or Markdown output for automation and human review.
  • CI-friendly decisions based on stable exit codes.

The project also documents integrations with Cursor, Windsurf, Codex, Claude Code, GitHub Actions, Hookshot, and MCP clients. These are documented setup targets, not claims of vendor endorsement.

Limitations and notes

A SAFE result is not proof that a package is harmless. Static analysis may miss a payload downloaded only after execution. The optional canary mode executes a package in a sandbox to confirm behavior, but it cannot prove that a package is safe. Listing an MCP server's tools, using the runtime proxy, and running the canary have different execution boundaries from normal guard and audit scans.

The pkgxray MCP server does not replace CVE-focused tools such as npm audit or OSV-Scanner; the README recommends running those alongside pkgxray.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Pkgxray

It does show that pkgxray is published on npm and can be run for CLI scans with `npx --yes pkgxray@1.0.5`.

Use the `mcp` command with a package target and the server command, such as `pkgxray mcp --package npm:some-mcp-server@1.4.2 npx some-mcp-server`. The `--recheck` option catches a later package change.

No. Normal `guard` and `audit` scans stage packages in quarantine and inspect them statically without running package code or lifecycle scripts.

`0` means SAFE, `2` means BLOCK, and `3` means REVIEW.

Yes. It supports PyPI targets and Python dependency files including `requirements.txt`, `poetry.lock`, `Pipfile.lock`, and `pyproject.toml`.

Related MCP servers

All in Security All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewPkgxray AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/pkgxray?style=directory)](https://allmcps.com/mcp/pkgxray)
HTML Embed
<a href="https://allmcps.com/mcp/pkgxray"><img src="https://allmcps.com/api/badge/pkgxray?style=directory" alt="Pkgxray on AllMCPs" /></a>