pkgproof

pkgproof-mcp

An MCP server that verifies an npm or PyPI package before you install it.

One tool, verify_package. It runs nine checks against pkgproof.net covering advisories, install scripts, typosquat and combosquat names, scope and declared-repository checks, and how the release differs from its predecessors, and answers safe, caution, block or does_not_exist with every reason labelled as fact or heuristic against its source.

The first verification each day is free and needs no configuration at all. No account, no key, no signup. Later calls the same day cost $0.05 in USDC, paid per call over x402, and only if you configure a wallet.

Install

Nothing to install or host: your MCP client runs the server itself. Needs Node 22 or newer.

Every release from 0.1.1 on is built and signed by CI and carries an npm provenance attestation tying the tarball to the commit and workflow run that produced it. A tool that vets other packages should be checkable the same way:

npm audit signatures

The server is also listed in the MCP Registry as net.pkgproof/pkgproof.

Free, no key

Add this to your MCP client configuration and you are done:

{

"mcpServers": { "pkgproof": { "command": "npx", "args": ["-y", "@pkgproof/mcp"] } } }

Claude Code

The repository is its own plugin marketplace, so there is no JSON to edit:

/plugin marketplace add jahija-okan/pkgproof-mcp

/plugin install pkgproof@pkgproof

The plugin runs the published package pinned to the version it was released beside, not whatever npx resolves to that day.

Claude Desktop

Releases carry a prebuilt .mcpb bundle on the releases page. Download it and open it: Desktop installs the server and holds the wallet keys in the OS secret store rather than in a plain-text configuration file.

The tool

verify_package, and nothing else. One call is one verification, so the daily allowance means the same thing here as it does over HTTP.

It answers twice over: a summary the agent reads, and the service's own JSON alongside it in structuredContent, under a declared output schema, carrying the verdict, every reason with its source, and the time the verdict was computed.

Calls run one at a time. The service allows one verification in flight per payer and refuses the second, so an agent walking a dependency list is queued here rather than failed.

Two networks

pkgproof settles on two chains, each on its own endpoint. They are not interchangeable: they take different key formats, and only one of them has a free tier.

How the server picks. The free attempt always goes to Base, because it is the only rail that answers an unpaid call. Payments prefer Algorand, and fall back to Base only when no Algorand key is configured. So a wallet on either chain works, and configuring neither still gets you a verdict a day.

Paid, with a wallet

[!WARNING]

Fund a throwaway wallet, never a main one. The key is stored in plain text

in your MCP client's configuration file, which is not an encrypted store, and

anything able to read that file can spend the wallet. Put in what you are

willing to spend on package verification and nothing more. There is

deliberately no spend cap in this server, so the wallet's own balance is the

only limit.

Algorand (preferred)

Verifications cost the account no ALGO. The 402 names a fee payer, so the facilitator covers the network fee on every payment and your ALGO balance does not move.

{

"mcpServers": { "pkgproof": { "command": "npx", "args": ["-y", "@pkgproof/mcp"], "env": { "PKGPROOF_ALGORAND_PRIVATE_KEY": "..." } } } }

Base

Send USDC on Base to the throwaway wallet's address. You do not need ETH: payment is an off-chain signature and the facilitator pays the gas.

{

"mcpServers": { "pkgproof": { "command": "npx", "args": ["-y", "@pkgproof/mcp"], "env": { "PKGPROOF_BASE_PRIVATE_KEY": "0x..." } } } }

The server always tries the free call first, so a configured wallet is only charged once the day's free verification is used up.

Configuration

With neither set, the server is free-tier only and says so once the day's verification is spent.

Easy setup, step by step

Needs Node 22 or newer. Use a throwaway account, as warned above.

1. Generate a throwaway Algorand account. This downloads a small helper script that creates a fresh account on your machine:

   git clone https://github.com/jahija-okan/pkgproof-x402-algorand

cd pkgproof-x402-algorand npm install npx tsx algo-account.ts new

It prints ADDRESS, KEY_B64 and MNEMONIC once and saves nothing. Keep them somewhere safe, such as a password manager. Use KEY_B64 everywhere below, never the 25-word MNEMONIC.

1. Send 0.3 ALGO to `ADDRESS`. Buy ALGO on an exchange and withdraw it on the Algorand network. A new account is empty and cannot do anything until it holds ALGO. This covers the account's minimum balance and the opt-in fee, and is a one-time cost. Verifications themselves cost no ALGO.

1. Opt the account into USDC. Algorand accounts must opt into an asset before they can receive it, so USDC sent to an account that has not opted in will not arrive. This command signs that opt-in with your key:

   ALGOD_URL=https://mainnet-api.algonode.cloud ASSET_ID=31566704 \

ALGO_PRIVATE_KEY= npx tsx algo-account.ts optin

1. Send USDC on Algorand to `ADDRESS`. Withdraw USDC from an exchange on the Algorand network, not Base or Ethereum. Each verification costs $0.05, so $1 covers 20 of them.

1. Check that both arrived. This reads the account from the network and prints its ALGO balance and USDC balance. NOT OPTED IN means step 3 did not go through:

   ALGOD_URL=https://mainnet-api.algonode.cloud ASSET_ID=31566704 \

npx tsx algo-account.ts balance

1. Add the server to Claude Code. This registers pkgproof as an MCP server and hands it the key, which it uses to sign payments on your machine and never sends anywhere. --scope user installs it for every project, without it, Claude Code registers the server for the current directory only:

   claude mcp add --scope user pkgproof -e PKGPROOF_ALGORAND_PRIVATE_KEY=<KEY_B64> -- npx -y @pkgproof/mcp

1. Run a verification. Start claude and ask: check package crossenv with pkgproof. Claude calls the verify_package tool and reports a verdict with its reasons.

The first verification each day is free and goes through Base. Later ones are paid from the Algorand account.

Privacy Policy

One HTTPS request per verification, carrying the package name, version and ecosystem you asked about and nothing else: no account, no telemetry, no file contents. Wallet keys are used to sign locally and are never transmitted. Full text in PRIVACY.md.

Development

npm install

npm test # unit tests, and a real client handshake over an in-memory transport npm run lint # typecheck, formatting, eslint npm run inspector # build, then the MCP inspector against the local server

No test spends anything, and the suite enforces it rather than trusting it: a test that reaches for the network fails, and the run refuses to start at all if a wallet key is set in the environment. The payment path is exercised against a fabricated 402 and a published test account, so an EIP-3009 authorisation is signed locally and the payload and header are checked without a wallet.

Links

• Service and docs: https://pkgproof.net/docs
• MCP Registry entry: https://registry.modelcontextprotocol.io/v0/servers?search=pkgproof
• OpenAPI, Base rail: https://x402.pkgproof.net/openapi.json
• OpenAPI, Algorand rail: https://x402-algo.pkgproof.net/openapi.json

License

Apache-2.0. If you distribute a modified version, section 4(b) requires you to mark the files you changed: a fork of a security tool that still carries this name should not be mistakable for this one.