Supply Chain Guard runs on your own machine — the client starts it, so there is no endpoint to ping. 1 696 installs a week from npm.
Supply-chain malware scanner and MCP server: vet packages in 15 ecosystems before install, offline.
The linked repository no longer exists on GitHub — it was deleted or made private.
We have not read this server's code yet, 3 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
tokens: [String.raw`(?:GetTickCount|IsDebuggerPresent|NtQueryInformationProcess|CheckRemoteDebuggerPresent)`],
const HOSTILE_TRAP_OPERATION = /\b(?:eval)\s*\(|\bnew\s+Function\b|\bfetch\s*\(|\baxios(?:\.\w+)?\s*\(|\bXMLHttpRequest\s*\(|\bchild_process\s*\.\s*(?:exec(?:File)?(?:Sync)?|spawn(?:Sync)?)\s*\(|\bexecSync\s*\(|\batob\s*\(/g;
const target = path.join(cacheDir, fileName);
const NPM_CREDENTIAL_PATH = /(?:\.npmrc(?![A-Za-z0-9_.\\/\-])|\bnpm_config_userconfig\b)/i;
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add supply-chain-guard -- npx -y supply-chain-guard
{
"mcpServers": {
"supply-chain-guard": {
"command": "npx",
"args": [
"-y",
"supply-chain-guard"
]
}
}
}
[mcp_servers.supply-chain-guard]
command = "npx"
args = ["-y", "supply-chain-guard"]
{
"mcpServers": {
"supply-chain-guard": {
"command": "npx",
"args": [
"-y",
"supply-chain-guard"
]
}
}
}
{
"servers": {
"supply-chain-guard": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"supply-chain-guard"
]
}
}
}
Scan AI agent skills, MCP server packages and MCP configs before you install them. Static analysis.
Scan for prompt injection, secrets, PII, and vet MCP servers before installation
Before an AI agent installs an npm/PyPI package: typosquat, vulnerability and existence checks.
MCP server for AI agents — Stacks, Celo, and Base in one npm package.
Pre-install security scans for npm packages, MCP servers, and AI agents with cited verdict evidence.
ScriptProbe: Check npm install scripts and publisher changes before installing.
Inspect an MCP server for common security risks before you install it. Offline, zero telemetry.
ecosyste.ms Packages MCP.
Answers built from our own checks of this server.