pkgproof
NPM · @PKGPROOF/MCP · SCANNED SEP 21
Verify an npm package before you install it: advisories, install scripts, typosquats, provenance.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security99
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 12 of 48 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to jahija-okan/pkgproof-mcp). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 6 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability83
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 153 tokens (~153/item across 1 items; 1 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management43
- Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the pkgproof MCP server?
pkgproof runs locally as an npm package, launched with npx -y @pkgproof/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pkgproof/mcp
claude mcp add net-pkgproof-pkgproof -- npx -y @pkgproof/mcp
{
"mcpServers": {
"net-pkgproof-pkgproof": {
"command": "npx",
"args": [
"-y",
"@pkgproof/mcp"
]
}
}
} {
"servers": {
"net-pkgproof-pkgproof": {
"command": "npx",
"args": [
"-y",
"@pkgproof/mcp"
]
}
}
} codex mcp add net-pkgproof-pkgproof -- npx -y @pkgproof/mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"net-pkgproof-pkgproof": {
"type": "local",
"command": [
"npx",
"-y",
"@pkgproof/mcp"
],
"enabled": true
}
}
} openclaw mcp add net-pkgproof-pkgproof --command npx --arg -y --arg @pkgproof/mcp
mcp_servers:
net-pkgproof-pkgproof:
command: "npx"
args: ["-y", "@pkgproof/mcp"] {
"McpServers": {
"net-pkgproof-pkgproof": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@pkgproof/mcp"
]
}
}
} assistant mcp add net-pkgproof-pkgproof -t stdio -c npx -a -y @pkgproof/mcp
{
"mcpServers": {
"net-pkgproof-pkgproof": {
"command": "npx",
"args": [
"-y",
"@pkgproof/mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 14 Sept 26 −14
- Malware scan: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: 0.17 → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- Package version: 0.1.4 → 0.1.7 functional
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +11
- Known CVEs: unverified → pass ▲ security
- Dependency health: unverified → 0.92 ▲ functional
- 9 Sept 26 +16
- Tool safety: pass → unverified ▼ security
- Malware scan: unverified → pass ▲ security
- Known CVEs: unverified → pass ▲ security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Stability: unverified → 0.03 ▲ functional
- Dependency health: unverified → 0.92 ▲ functional
- First check of Schema quality: unverified functional
- Package version: 0.1.3 → 0.1.4 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Sept 2026 · Analysed npm/@pkgproof/mcp@0.1.7
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | jahija-okan/pkgproof-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/jahija-okan/pkgproof-mcp/.github/workflows/publish.yml@refs/tags/v0.1.7 |
| Rekor log index | 2831141816 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:f90c8603db6985283ebdb3212f9ff2e4693b83b7c9fd90c134e05a74f1653be88306f50f5c56feb9858be3f97261c2b95cd0cb81bc3e026fb7c8cee25 |
Background: How many MCP packages publish verified provenance →
Dependencies 48 packages
| Packages resolved | 48 |
|---|---|
| Stale | 12 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
verify_package Verify package ~153
Verify an npm package before installing it. Runs eight checks covering advisories, install scripts, typosquat and combosquat names, scope, repository provenance and maintainer reputation, 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.
| Name | Type | Req | Description |
|---|---|---|---|
| ecosystem | string | – | Package ecosystem. Only npm is supported. |
| name | string | yes | Package name, scoped or not: left-pad, @scope/thing. |
| version | string | – | Exact version to verify. Omit to verify the package rather than one release. |
| Name | Type | Req | Description |
|---|---|---|---|
| checked_at | string | yes | When the verdict was computed, ISO 8601 UTC. |
| ecosystem | string | yes | – |
| name | string | yes | – |
| reasons | array | yes | Every reason behind the verdict. |
| sources | object | yes | The datasets consulted, by name and URL. |
| verdict | string | yes | – |
| version | string|null | yes | The version verified, or null if none was given. |
No examples provided.
What is the pkgproof MCP server?
pkgproof is an MCP server listed in the public MCP registry as net.pkgproof/pkgproof. Verify an npm package before you install it: advisories, install scripts, typosquats, provenance. This page covers its npm package (@pkgproof/mcp).
Is the pkgproof MCP server safe to use?
pkgproof scores 88 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the pkgproof MCP server expose?
pkgproof exposes 1 tool: verify_package. Their descriptions and schemas cost roughly 153 tokens of context every time the server is loaded.
Is the pkgproof MCP server still maintained?
pkgproof is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the pkgproof MCP server under?
pkgproof declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.