# supply-chain-guard

**Category:** 🔒 Security  
**Repository:** https://github.com/homeofe/supply-chain-guard  
**GitHub Stars:** 7  
**npm Downloads (last month):** 5117  
**Views:** 9  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/supply-chain-guard

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

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

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

## Documentation

## What the supply-chain-guard MCP server does

The supply-chain-guard MCP server connects an AI coding agent to a locally running supply-chain security scanner. It is designed to help an agent inspect packages and other installable components before they enter a project. The scanner checks package, extension, plugin, provider, container image, and GitHub Actions identities against a signed threat feed.

Coverage includes npm, PyPI, RubyGems, Composer, NuGet, Cargo, Go modules, JVM build ecosystems, Dart and Flutter, Terraform and OpenTofu providers, container images, GitHub Actions, VS Code and Open VSX extensions, browser extensions, and JetBrains plugins. Matchers also exist for additional ecosystems that may report findings when matching indicators become available.

The scanner reads manifests and lockfiles at any depth in a repository. Lockfile analysis includes pinned transitive dependencies, not only direct dependencies. Detection covers known malicious releases and more than 350 threat indicators, including markers associated with GlassWorm, Vidar, Shai-Hulud, fake AI tool repositories, and account-takeover activity.

## How it works

The supply-chain-guard MCP server runs the scanner locally through the package's MCP command. The scan itself makes no network request, so it can be used in environments where source and dependency data must remain local. Threat data is maintained separately: a daily feed can be refreshed when network access is available, then imported into an offline or air-gapped environment.

A version-specific match is required for a package release to be identified as malicious. The scanner keeps registry-specific identities separate and can match commit SHAs or container image digests independently of repository names. Beyond identity matching, it can generate CycloneDX 1.6 SBOMs, assess SLSA provenance, validate in-toto and DSSE attestations structurally, and correlate findings into attack-chain incidents.

## Setup and configuration

Install the npm package globally, then register its MCP command with an AI coding client. The documented Claude setup is:

```bash
npm install -g supply-chain-guard
claude mcp add supply-chain-guard supply-chain-guard mcp
```

The package requires Node.js 22 or newer. A project can also be scanned directly with `supply-chain-guard scan .`. Refresh the signed threat feed regularly with `supply-chain-guard feed refresh`; the scanner uses the cached feed for later scans. For disconnected networks, signed feed files can be transferred and loaded with the feed import workflow.

Avoid starting `npx`, `npm exec`, or `npm run` from inside an untrusted directory. The README warns that npm can place that directory's `node_modules/.bin` first on `PATH` before the scanner starts.

## Tools and capabilities

For developers evaluating the supply-chain-guard MCP server in the Security category, relevant capabilities include:

- Vetting packages and project dependencies before installation.
- Scanning manifests and lockfiles throughout a repository.
- Matching known-malicious components across supported ecosystems.
- Producing CycloneDX 1.6 software bills of materials.
- Checking SLSA provenance and parsing in-toto or DSSE attestations.
- Correlating related findings into attack-chain incidents.

## Limitations and notes

Detection depends on the signed feed and the indicators it contains. A scan exits with status 1 for a high-severity finding or an incomplete examination, and status 2 for a critical finding, which can support CI gating. The project is licensed under Apache 2.0.

_Full upstream README: https://allmcps.com/mcp/supply-chain-guard/readme_