pkgproof

Name: pkgproof
Author: jahija-okan

by jahija-okanversion 0.2.1i★ –iRuns on your computer

Registry namenet.pkgproof/pkgproof

Install

Overview

Description from the maker (original English)

Verify an npm or PyPI package before install: advisories, install scripts, typosquats, repository.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Other
You need to fill in: PKGPROOF_ALGORAND_PRIVATE_KEY, PKGPROOF_BASE_PRIVATE_KEY

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
You fill in yourself: PKGPROOF_ALGORAND_PRIVATE_KEY, PKGPROOF_BASE_PRIVATE_KEY

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

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

Run this in your terminal

claude mcp add pkgproof --env PKGPROOF_ALGORAND_PRIVATE_KEY=your-value --env PKGPROOF_BASE_PRIVATE_KEY=your-value -- npx -y @pkgproof/mcp

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

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

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "pkgproof": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@pkgproof/mcp"
      ],
      "env": {
        "PKGPROOF_ALGORAND_PRIVATE_KEY": "your-value",
        "PKGPROOF_BASE_PRIVATE_KEY": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

PKGPROOF_ALGORAND_PRIVATE_KEY secret env
Base64 account key of a throwaway Algorand wallet holding USDC (ASA 31566704) on Algorand Mainnet. Not a 25-word mnemonic. Optional: the first verification each day is free without any key. This is t…
PKGPROOF_BASE_PRIVATE_KEY secret env
0x-prefixed private key of a throwaway EVM wallet holding USDC on Base. Optional, and only used when no Algorand key is configured. Needs no ETH: payment is an off-chain signature and the facilitator…

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified against the domain pkgproof.net (the registry checks domain ownership)
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

More stars than 0% of the other 32583 servers in this category
Published to the registry more recently than 63% of the other 32583 servers in this category
Basic checks equal to or better than 100% of the other 32583 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is pkgproof safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: PKGPROOF_ALGORAND_PRIVATE_KEY, PKGPROOF_BASE_PRIVATE_KEY

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.2.1) reached the registry 22 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, sync. labs

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated yesterday

Install

sync. labs

by synchronicity-labs

Lipsync videos, dub them into other languages, make talking videos and open sync. Studio.

Computer or cloudUpdated today

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

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.

Argument	Required	Meaning
`name`	yes	Package name: `left-pad`, `@scope/thing` (npm), `requests` (PyPI).
`version`	no	Exact version. Omit to verify the package rather than one release.
`ecosystem`	no	`npm` (the default) or `pypi`.

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.

	Algorand Mainnet	Base
Endpoint	`x402-algo.pkgproof.net`	`x402.pkgproof.net`
Network	`algorand:wGHE2Pwdvd7S12BL5FaOP20EGYesN73ktiC1qzkkit8=`	`eip155:8453`
Asset	USDC, ASA `31566704`	USDC, `0x8335…2913`
Price	$0.05 per verification	$0.05 per verification
Free tier	no, every call is paid	yes, one verdict per caller per day
Key variable	`PKGPROOF_ALGORAND_PRIVATE_KEY`	`PKGPROOF_BASE_PRIVATE_KEY`
Key format	base64 account key	`0x`-prefixed EVM key
Network fee per payment	none, sponsored	none, sponsored
One-time setup	~0.3 ALGO, and an opt-in to the asset	none, just send USDC

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

Variable	Required	Meaning
`PKGPROOF_ALGORAND_PRIVATE_KEY`	no	Throwaway Algorand account holding USDC on Mainnet, base64. Preferred for payment when set.
`PKGPROOF_BASE_PRIVATE_KEY`	no	Throwaway EVM wallet holding USDC on Base, `0x`-prefixed. Used when no Algorand key is set.

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.

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.

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.

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

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.

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

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

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.

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.

pkgproof

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

sync. labs

README from the maker

pkgproof-mcp

Install

Free, no key

Claude Code

Claude Desktop

The tool

Two networks

Paid, with a wallet

Algorand (preferred)

Base

Configuration

Easy setup, step by step

Privacy Policy

Development

Links

License