pkgproof
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PKGPROOF_BASE_PRIVATE_KEY | No | Throwaway EVM wallet holding USDC on Base, 0x-prefixed. Used when no Algorand key is set. | |
| PKGPROOF_ALGORAND_PRIVATE_KEY | No | Throwaway Algorand account holding USDC on Mainnet, base64. Preferred for payment when set. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| verify_packageA | Verify an npm or PyPI package before installing it. Runs up to nine checks 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. One call is one verification: the first each day is free, and later ones cost $0.05 in USDC when a wallet is configured. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only a single tool, there is no possibility of confusing it with another operation. Its purpose (verify an npm/PyPI package before install) is stated precisely, so misselection is not a concern.
verify_package uses a clean, predictable verb_noun snake_case pattern. A one-tool surface cannot exhibit convention mixing, so consistency is trivially perfect.
One tool is thin for a server, even though the tool deliberately aggregates nine checks and four verdicts into a single call. It is defensible as a focused single-purpose service, but it sits at the borderline of feeling under-scoped.
The single call covers the core verification lifecycle well: advisories, install scripts, typosquat/combosquat, scope, repository, and release diffing, with labelled fact/heuristic reasoning. Minor gaps remain (no batch/multi-package verification, no result caching or history retrieval), but agents can work around them.