PkgGuard
NPM · @AGENTGATE-BUILDER/PKGGUARD · 2 COMPONENTS
Dependency scan for agents: known CVEs and malicious packages via OSV.dev. By Crypto Money Maker
Available components
Last scanned (3 hours ago)
Scores higher than 36% of npm servers
Category Security
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 Security100
- 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
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency19
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 1 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability58
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 415 tokens (~207/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage83
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 50% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 22 Oct 26 61
First indexed and scored.
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 23 Oct 2026 · Analysed npm/@agentgate-builder/pkgguard@0.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| 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 →
check_package Is this package version vulnerable or malicious? ~92
Checks one package version (npm, PyPI, Go, crates.io, Packagist, RubyGems, Maven, NuGet, Pub, Hex) against OSV.dev. Paid mode uses https://api.youraitools.co/pkgguard/v1/package ($0.001).
| Name | Type | Req | Description |
|---|---|---|---|
| ecosystem | string | – | default npm |
| name | string | yes | – |
| version | string | yes | – |
No output schema declared.
No examples provided.
scan_dependencies Scan a dependency manifest for vulnerable and malicious packages ~260
Checks a package.json, lockfile, requirements.txt, go.mod, Cargo.lock, poetry.lock or composer.lock (contents or a local path) or a package list against OSV.dev for known vulnerabilities and confirmed-malicious packages. Free preview by default (verdict and counts, up to 25 packages). With PKGGUARD_X402_PRIVATE_KEY set, returns the full paid result (affected packages, advisory ids, severity, CVSS, fixed-in versions; up to 500 packages) from https://api.youraitools.co/pkgguard/v1/scan, paying $0.003 USDC on Base per scan over x402. Informational: lists published advisories from OSV.dev for the versions given. Not a security audit; a clean result does not prove a package is safe.
| Name | Type | Req | Description |
|---|---|---|---|
| filename | string | – | – |
| include_dev | boolean | – | – |
| manifest | string | – | File contents (package.json, package-lock.json, requirements.txt, Pipfile.lock, poetry.lock, go.mod, Cargo.lock, composer.lock) |
| packages | array | – | [{ecosystem, name, version}] |
| path | string | – | Or a local file path to read (e.g. ./package-lock.json) |
No output schema declared.
No examples provided.
How do I install the PkgGuard MCP server?
PkgGuard runs locally as an npm package, launched with npx -y @agentgate-builder/pkgguard. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @agentgate-builder/pkgguard
claude mcp add co-youraitools-pkgguard -- npx -y @agentgate-builder/pkgguard
What is the PkgGuard MCP server?
PkgGuard is an MCP server listed in the public MCP registry as co.youraitools/pkgguard. Dependency scan for agents: known CVEs and malicious packages via OSV.dev. By Crypto Money Maker. This page covers its npm package (@agentgate-builder/pkgguard).
Is the PkgGuard MCP server safe to use?
PkgGuard scores 61 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 23 October 2026. It declares no install or post-install scripts. 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 PkgGuard MCP server expose?
PkgGuard exposes 2 tools: scan_dependencies, check_package. Their descriptions and schemas cost roughly 352 tokens of context every time the server is loaded.
Is the PkgGuard MCP server still maintained?
PkgGuard is still listed as active in the MCP registry. We last reached this channel on 23 October 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 PkgGuard MCP server under?
PkgGuard declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.