npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

pkgproof-mcp

v0.0.1

Published

MCP server (verify_package) — the agent-loop guard that blocks hallucinated/slopsquatted npm installs.

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

eastvillagetecheastvillagetech

Keywords

mcpmodel-context-protocolnpmsecuritysupply-chainslopsquattingai-codingclaude

Readme

pkgproof-mcp

The agent-loop install guard — an MCP server exposing verify_package so a coding agent (Claude Code, Cursor, VS Code) checks an npm package before it installs it or edits package.json.

⚠️ Pre-alpha (v0.0.1) — not for production use

pkgproof is under active development. Verdicts, APIs, and the bundled blocklist will change without notice. This early release reserves the name and shares progress — please don't depend on it yet.

On BLOCK the agent stops; on WARN it confirms with the user; on ALLOW it proceeds. Same deterministic, explainable verdict engine as the pkgproof CLI.

Pre-alpha on npm. Published under the alpha tag as v0.0.1: npm install -g pkgproof-mcp@alpha. Or build from source — see the repo README.

Setup

pkgproof init claude        # or: cursor | vscode  — wires this server into your editor's MCP config

Add to your project rules (CLAUDE.md / .cursorrules):

"Before any npm/pnpm/yarn install or package.json dependency edit, call verify_package. If it returns BLOCK, do NOT install — stop and tell the user why."

The verify_package contract

Input: { name: string }. Output is BOTH a human/agent directive (text) and machine-readable structuredContent (documented by the tool's outputSchema):

| field | type | meaning | |---|---|---| | verdict | "ALLOW" \| "WARN" \| "BLOCK" | the install decision — BLOCK means DO NOT install | | package | string | the name checked | | reason | string | ≤120 chars; quote verbatim to the user | | confidence | number | 0..1 | | suggestion | string | null | nearest real package when the name is a likely typo | | blocklist_loaded | number | count of confirmed-malicious names in the loaded signature blocklist | | gate_ok | boolean | true only if the blocklist loaded non-empty. If false, signature coverage is DOWN and an ALLOW is not malware-verified — the ALLOW directive degrades to say so. Do not silently trust it. |

Environment

  • PKGPROOF_BLOCKLIST — optional path to override where the signature blocklist is loaded from. If it points at a missing/empty file, the gate runs degraded: gate_ok is false, every ALLOW carries a "confirmed-malware coverage is DOWN" warning, and the startup log prints GATE EMPTY. Leave it unset for normal resolution (the bundled blocklist.json).

Apache-2.0.