Supply Chain Guard

io.github.homeofePublished by GitHub account homeofev6.6.1Updated Oct 30, 2026

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

The publisher's own server: Agent.chain.tokyo Address Contracts

VerifiedSTDIODesktop onlyDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

Offline supply-chain malware scanner exposed as an MCP server, letting an assistant vet packages across 15 ecosystems before installing them.

What you can do
  • Check packages for malware and supply-chain risk before they are installed
  • Cover packages from 15 different package ecosystems
  • Run the checks offline, without sending package data to an external service
When to use it
Useful when an assistant helps add or upgrade dependencies and you want a pre-install safety check on unfamiliar packages. Suited to teams that prefer offline scanning over uploading package names to a hosted service.
Requirements
Runs as a local process over stdio, installed from the npm package supply-chain-guard, so Node.js and npm are needed on the machine. No authentication, environment variables or headers are declared. Desktop-only; not available as a web executable.
Before you install
The manifest lists no tools, so the exact operations and their side effects are not documented here. It is a scanner, not a guarantee: treat its verdicts as one signal among others. No credentials are requested, and the description says scanning is offline.

Installation

In SourceWeft

  1. Open Supply Chain Guard in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

21
  1. v6.6.1LatestOct 29, 2026
  2. v6.6.0Oct 21, 2026
  3. v6.5.10Oct 21, 2026
  4. v6.5.9Oct 18, 2026
  5. v6.5.8Oct 16, 2026
  6. v6.5.7Oct 14, 2026
  7. v6.5.6Oct 13, 2026
  8. v6.5.5Oct 13, 2026
  9. v6.5.4Oct 11, 2026
  10. v6.5.3Oct 9, 2026
  11. v6.5.2Oct 8, 2026
  12. v6.5.1Oct 6, 2026
  13. v6.5.0Oct 5, 2026
  14. v6.4.3Oct 4, 2026
  15. v6.4.2Oct 3, 2026
  16. v6.4.1Oct 2, 2026
  17. v6.4.0Sep 30, 2026
  18. v6.3.3Sep 29, 2026
  19. v6.3.2Sep 28, 2026
  20. v6.3.1Sep 26, 2026
  21. v6.3.0Sep 26, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Chain integrations