Semgrep vs Supply Chain Guard

A side-by-side look at the Semgrep and Supply Chain Guard MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Semgrep logoSemgrepSecurity · Local subprocess (stdio)Scan code for security vulnerabilities using Semgrep.48FairAuth: no auth requiredSupply Chain Guard logoSupply Chain GuardSecurity · Local subprocess (stdio)Supply-chain malware scanner and MCP server: vet packages in 15 ecosystems before install, offline.51GoodAuth: no auth required

Verdict: choose Semgrep for security work as a local process; choose Supply Chain Guard for security as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Semgrep logoChoose Semgrep when

  • You need dedicated capabilities in the Security domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
Explore Semgrep

Supply Chain Guard logoChoose Supply Chain Guard when

  • You need dedicated capabilities in the Security domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
Explore Supply Chain Guard

Feature & specification comparison

Rows where the two servers differ are marked.

SpecSemgrep logoSemgrepSupply Chain Guard logoSupply Chain Guard
CategorySecuritySecurity
Quality signal48/100 · Fair51/100 · Good
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNo auth requiredNo auth required
PricingFreeFree
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars17,1467
Directory activity 1 views 0 installs 0 upvotes 4 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

Semgrep tools

No tool names declared yet. Check the project README from the listing page.

Supply Chain Guard tools

No tool names declared yet. Check the project README from the listing page.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Semgrep

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "semgrep-semgrep": {
      "command": "uvx",
      "args": [
        "semgrep"
      ]
    }
  }
}

Supply Chain Guard

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "supply-chain-guard": {
      "command": "npx",
      "args": [
        "-y",
        "supply-chain-guard"
      ]
    }
  }
}

Frequently asked questions

Semgrep is categorized under Security and uses a local stdio subprocess. Supply Chain Guard belongs to Security and uses a local stdio subprocess. Pick Semgrep for security work and Supply Chain Guard for security.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Semgrep is listed as free. Auth: no auth required. Supply Chain Guard is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add semgrep-semgrep and supply-chain-guard as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Semgrep has a quality signal of 48/100 (Fair) with 1 views, 0 installs and 17,146 GitHub stars. Supply Chain Guard has 51/100 (Good) with 4 views, 0 installs and 7 GitHub stars.