# io.github.homeofe/supply-chain-guard (npm · supply-chain-guard)

Supply-chain malware scanner and MCP server: vet packages in 15 ecosystems before install, offline.

- Trust score: 82/100 (high trust)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-01

## Components

- npm · `supply-chain-guard`: 82/100 (this document), [markdown](https://verifymcp.io/servers/homeofe-supply-chain-guard/supply-chain-guard.md), [page](https://verifymcp.io/servers/homeofe-supply-chain-guard/supply-chain-guard)

## Channel facts

- Registry: `npm`
- Package: `supply-chain-guard`
- Version: `6.4.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-10-01.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 0 of 1 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to homeofe/supply-chain-guard).
  - Clear OSI-approved license (Apache-2.0).
  - Actively maintained (last published 0 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 623 tokens (~207/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 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.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the io.github.homeofe/supply-chain-guard MCP server?

io.github.homeofe/supply-chain-guard runs locally as an npm package, launched with npx -y supply-chain-guard. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add homeofe-supply-chain-guard -- npx -y supply-chain-guard
```

### Cursor

```json
{
  "mcpServers": {
    "homeofe-supply-chain-guard": {
      "command": "npx",
      "args": [
        "-y",
        "supply-chain-guard"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "homeofe-supply-chain-guard": {
      "command": "npx",
      "args": [
        "-y",
        "supply-chain-guard"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add homeofe-supply-chain-guard -- npx -y supply-chain-guard
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add homeofe-supply-chain-guard --command npx --arg -y --arg supply-chain-guard
```

### Hermes

```yaml
mcp_servers:
  homeofe-supply-chain-guard:
    command: "npx"
    args: ["-y", "supply-chain-guard"]
```

### Netclaw

```json
{
  "McpServers": {
    "homeofe-supply-chain-guard": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "supply-chain-guard"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add homeofe-supply-chain-guard -t stdio -c npx -a -y supply-chain-guard
```

### Other

```json
{
  "mcpServers": {
    "homeofe-supply-chain-guard": {
      "command": "npx",
      "args": [
        "-y",
        "supply-chain-guard"
      ]
    }
  }
}
```

## 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-10-01 (score 82, +12)

- [security improvement] Known CVEs: unverified → pass
- [functional improvement] Dependency health: unverified → 1.00

### 2026-09-30 (score 70, +16)

- [security improvement] Malware scan: unverified → pass
- [security improvement] Known CVEs: unverified → pass
- [functional improvement] Dependency health: unverified → 1.00
- [functional] Package version: 6.3.3 → 6.4.0

### 2026-09-29 (score 54, 0)

- [security improvement] Malware scan: unverified → pass
- [security improvement] Known CVEs: unverified → pass
- [functional improvement] Dependency health: unverified → 1.00
- [functional] Package version: 6.3.2 → 6.3.3

### 2026-09-28 (score 54, −25)

- [security regression] Malware scan: pass → unverified
- [security regression] Known CVEs: pass → unverified
- [functional regression] Dependency health: 1.00 → unverified
- [functional improvement] Stability: unverified → 0.07
- [functional] Package version: 6.3.1 → 6.3.2
- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-26 (score 79)

First indexed and scored.

## MCP tools (3)

### `ioc_lookup` (~309 tokens)

Offline lookup against supply-chain-guard's threat intelligence and known-bad version blocklist. No network access. It always consults the bundled indicators (recent and curated ones, including every domain, url, ip and hash); package indicators older than the bundle window are in a historical catalog that is only consulted once `supply-chain-guard feed refresh` has downloaded it. Two modes: pass {ecosystem, name} to check a PACKAGE before installing/importing/recommending it, or pass {indicator} to check a single domain/url/ip/hash observed in code or logs. Returns a malicious/clean verdict with matched campaign and malware family details, and checkedAgainst.catalog says whether the catalog was consulted. Names are read the way the scanners read them: docker takes an image reference (any registry host) with the tag or sha256: digest as version; terraform and tfmodule take a registry address; swift takes the repository URL; actions takes owner/repo with the commit SHA as version.

Input parameters:

- `ecosystem` (string): Package ecosystem the name belongs to (package-mode)
- `indicator` (string): A single domain, url, ip, or hash to look up against the feed (indicator-mode). Use INSTEAD of ecosystem/name.
- `name` (string): Package name, e.g. 'event-stream' or '@scope/pkg' (package-mode)
- `version` (string): Exact version to check (optional, package-mode). Without it only version-independent IOCs match.

### `scan_directory` (~134 tokens)

Run supply-chain-guard's full static malware scan (350+ detection rules: obfuscation, install hooks, C2 indicators, lockfile tampering, CI/CD abuse) over a local directory. Local filesystem only. Returns a compact JSON summary with risk score, findings count by severity, and the top findings.

Input parameters:

- `minSeverity` (string): Only report findings at or above this severity (optional)
- `path` (string, required): Local directory path to scan
- `since` (string): Only scan files changed since this git commit/ref (optional diff scan, e.g. 'HEAD~1' or a SHA).

### `scan_npm_package` (~117 tokens)

Scan an npm package WITHOUT installing it. NOTE: this downloads metadata and the tarball of the latest published version from the npm registry (network access). Also runs the offline IOC lookup for the given name (and exact version, if provided; the deep content scan always analyzes the latest published version).

Input parameters:

- `name` (string, required): npm package name, e.g. 'express' or '@scope/pkg'
- `version` (string): Exact version for the offline IOC check (optional). The remote deep scan targets the latest published version regardless.

## Diagnostics

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

## Score history

- 2026-10-01: 82
- 2026-09-30: 70
- 2026-09-29: 54
- 2026-09-28: 54
- 2026-09-27: 79
- 2026-09-26: 79

## Common questions

### What is the io.github.homeofe/supply-chain-guard MCP server?

io.github.homeofe/supply-chain-guard is an MCP server listed in the public MCP registry as io.github.homeofe/supply-chain-guard. Supply-chain malware scanner and MCP server: vet packages in 15 ecosystems before install, offline. This page covers its npm package (supply-chain-guard).

### Is the io.github.homeofe/supply-chain-guard MCP server safe to use?

io.github.homeofe/supply-chain-guard scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 1 October 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 io.github.homeofe/supply-chain-guard MCP server expose?

io.github.homeofe/supply-chain-guard exposes 3 tools: ioc_lookup, scan_directory, scan_npm_package. Their descriptions and schemas cost roughly 560 tokens of context every time the server is loaded.

### Is the io.github.homeofe/supply-chain-guard MCP server still maintained?

io.github.homeofe/supply-chain-guard is still listed as active in the MCP registry. We last reached this channel on 1 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 io.github.homeofe/supply-chain-guard MCP server under?

io.github.homeofe/supply-chain-guard 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.

## Links

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