# io.github.mlawsonking/package-guard-mcp (npm · package-guard-mcp)

Supply-chain guard for AI coding agents: verify packages, check vulns/malware, detect typosquats.

- Trust score: 66/100 (medium)
- Change this week: +20
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- npm · `package-guard-mcp`: 66/100 (this document), [markdown](https://verifymcp.io/servers/mlawsonking-package-guard-mcp/package-guard-mcp.md), [page](https://verifymcp.io/servers/mlawsonking-package-guard-mcp/package-guard-mcp)

## Channel facts

- Registry: `npm`
- Package: `package-guard-mcp`
- Version: `1.2.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Supply Chain Security**: 87/100
  - No malware found by supply-chain analysis.
  - Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.
  - No install/post-install scripts declared.
  - Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 2 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 63/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1216 tokens (~243/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add mlawsonking-package-guard-mcp -- npx -y package-guard-mcp
```

### Codex

```bash
codex mcp add mlawsonking-package-guard-mcp -- npx -y package-guard-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "mlawsonking-package-guard-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "package-guard-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add mlawsonking-package-guard-mcp --command npx --arg -y --arg package-guard-mcp
```

### Hermes

```yaml
mcp_servers:
  mlawsonking-package-guard-mcp:
    command: "npx"
    args: ["-y", "package-guard-mcp"]
```

### Other

```json
{
  "mcpServers": {
    "mlawsonking-package-guard-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "package-guard-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-02 (score 66, +48)

- [security regression] Provenance: unverified → fail
- [security improvement] Install scripts: unverified → pass
- [security improvement] Known CVEs: unverified → partial
- [security improvement] Malware scan: unverified → pass
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Maintenance: unverified → pass
- [functional improvement] Stability: unverified → 0.20
- [functional improvement] Dependency health: unverified → partial
- [functional improvement] License: unverified → pass
- [functional improvement] Schema quality: unverified → excellent
- [functional] Licence: MIT

### 2026-08-01 (score 18, −7)

- [security regression] Stability: 0.13 → unverified
- [functional regression] Capabilities: pass → unverified

### 2026-07-31 (score 25, −21)

- [security regression] Malware scan: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified
- [functional] Package version: 1.0.1 → 1.1.0
- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-27 (score 46)

First indexed and scored.

## MCP tools (5)

### `verify_package` (~346 tokens)

The pre-install guard for npm and PyPI. Call it before installing or recommending a package. Returns safe, caution or danger from deterministic checks: is the name registered, does OSV hold vulnerability or malware advisories for it, how old is it, weekly downloads, deprecation, license. If the name is not in the registry, likely_hallucination is set and npm names come with a "did you mean" list (PyPI names get an empty list). That flag means "not in this registry" and cannot tell an AI-invented name from a typo, a rename, or a package that only lives in a private registry. The slopsquat and typosquat score is a heuristic, not a finding: it adds up age under 90 days, under 50 weekly downloads, and a name within 2 edits of an npm search hit, so it both false-alarms on new legitimate packages and misses well-aged malicious ones. Package contents are never downloaded or analysed, so a malicious package with no OSV advisory reads as safe here. vulnerabilities.checked=false with count=null means the OSV lookup failed and the package was NOT checked: treat that as unknown, not as clean. Network: needs registry.npmjs.org, pypi.org, api.osv.dev.

Input parameters:

- `ecosystem` (string): Package ecosystem: npm or pypi (default npm). Other ecosystems have no registry client here. Use check_vulns for those.
- `name` (string, required): Package name (e.g. "express", "@scope/pkg", "requests").
- `version` (string): Specific version to check vulns against (default: latest).

### `check_vulns` (~184 tokens)

Known vulnerabilities and malware advisories for a package, optionally for one version, from the OSV.dev database. This is the one tool here that is correct for all seven ecosystems it accepts (npm, PyPI, Go, crates.io, RubyGems, Maven, NuGet), because it queries OSV directly and never touches a registry. It therefore cannot tell you whether the package exists, who publishes it, or whether it is maintained. An empty list means OSV held nothing for that name and version, not that the package is safe: OSV only knows what has been reported. A failed lookup returns an error and never an empty list. Network: needs api.osv.dev.

Input parameters:

- `ecosystem` (string): Package ecosystem (default npm).
- `name` (string, required): Package name.
- `version` (string): Version (omit to check all versions).

### `package_info` (~168 tokens)

Registry metadata for an npm or PyPI package: latest version, first and last publish dates, age, weekly downloads, deprecation, license, repository and description. Use it to judge whether a dependency is maintained. It makes no security judgement and runs no vulnerability lookup. Weekly downloads come from api.npmjs.org or pypistats.org and the field is simply absent when those are unavailable, so a missing weekly_downloads is not a zero. License and repository are whatever the publisher declared, unverified. Network: needs registry.npmjs.org, pypi.org.

Input parameters:

- `ecosystem` (string): Package ecosystem: npm or pypi (default npm). Other ecosystems have no registry client here. Use check_vulns for those.
- `name` (string, required): Package name.

### `audit_deps` (~270 tokens)

Audit a set of npm or PyPI dependencies in one call. Give it a list of names, or the text of a package.json (its dependencies and devDependencies), or the text of a requirements.txt. Returns a per-package report (exists, vulns, malicious, deprecated, verdict, flags) and a summary. Direct entries only: no lockfile is parsed and no transitive dependency is resolved, so this is not a full-tree audit and a vulnerable grandchild dependency will not appear. First 40 names, the rest are dropped and truncated is set. A version range is reduced to the digits inside it, so ^4.17.20 is checked as 4.17.20 and the real resolved version may differ. When the batch OSV call fails, every package reports vulns=null with vulns_checked=false rather than a reassuring zero. Network: needs registry.npmjs.org, pypi.org, api.osv.dev.

Input parameters:

- `ecosystem` (string): Package ecosystem: npm or pypi (default npm). Other ecosystems have no registry client here. Use check_vulns for those.
- `packageJson` (string): Raw package.json content.
- `packages` (array): List of package names.
- `requirements` (string): Raw requirements.txt content.

### `typosquat_scan` (~248 tokens)

Generate lookalike names around an npm or PyPI package and report which ones are actually registered and which look recent enough to be suspicious. The variants are heuristic and ASCII only: single-character deletions, adjacent transpositions, doubled letters, the swaps l/1, o/0, rn/m, -/_, ./-, i/l and s/z, and the name with every hyphen or underscore dropped. Up to 20 variants, no Unicode homoglyphs, no prefix or suffix squats such as name-js or python-name, so an empty result is not evidence that nobody is squatting the name. "suspicious" means only that the variant is registered and is either under a year old or has no creation date, which catches new squats and also flags legitimate new packages. Registration is not evidence of malice: nothing here inspects what a variant contains. Network: needs registry.npmjs.org, pypi.org.

Input parameters:

- `ecosystem` (string): Package ecosystem: npm or pypi (default npm). Other ecosystems have no registry client here. Use check_vulns for those.
- `name` (string, required): Package name to scan around.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/mlawsonking-package-guard-mcp/package-guard-mcp#diagnostics

## Score history

- 2026-08-03: 66
- 2026-08-02: 66
- 2026-08-01: 18
- 2026-07-31: 25
- 2026-07-29: 46
- 2026-07-28: 46
- 2026-07-27: 46

## Links

- npm package: https://www.npmjs.com/package/package-guard-mcp
- Socket report: https://socket.dev/npm/package/package-guard-mcp
- Repository: https://github.com/mlawsonking/MCP
- Changelog RSS feed: https://verifymcp.io/servers/mlawsonking-package-guard-mcp/package-guard-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/mlawsonking-package-guard-mcp/package-guard-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/mlawsonking-package-guard-mcp/package-guard-mcp