Agent Security Scanner MCP vs Supply Chain Guard

A side-by-side look at the Agent Security Scanner MCP 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.

Agent Security Scanner MCP logoAgent Security Scanner MCPSecurity · Local subprocess (stdio)Security layer for AI agents: blocks prompt injection, detects fake packages, scans vulnerabilities.68GreatAuth: not declaredSupply 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 Agent Security Scanner MCP 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?

Agent Security Scanner MCP logoChoose Agent Security Scanner MCP when

  • You need dedicated capabilities in the Security domain.
  • You prefer a local stdio subprocess transport.
  • You want tools like scan_security, fix_security, record_security_outcome.
Explore Agent Security Scanner MCP

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.

SpecAgent Security Scanner MCP logoAgent Security Scanner MCPSupply Chain Guard logoSupply Chain Guard
CategorySecuritySecurity
Quality signal68/100 · Great51/100 · Good
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNo auth required
PricingNot declaredFree
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars1247
Directory activity 2 views 0 installs 0 upvotes 4 views 0 installs 0 upvotes
Tools23Not listed

Tools & capabilities

Agent Security Scanner MCP tools 23

  • scan_securityScan a file for security vulnerabilities. Use verbosity='minimal' for counts only (~50 tokens), 'compact' (default) for actionable info (~200 tokens), 'full' for complete metadata.
  • fix_securityScan a file and return fixes. Use verbosity='minimal' for summary only, 'compact' (default) for fix list, 'full' for complete fixed file content.
  • record_security_outcomeRecord aggregate remediation outcomes after reviewing scanner findings. Sends counts only; never sends code, findings, paths, or rule IDs.
  • list_security_rulesList all available security fix templates and their descriptions
  • check_packageCheck if a package name is legitimate or potentially hallucinated (AI-invented)
  • scan_packagesScan code for package imports and check for hallucinated (AI-invented) packages. Use verbosity='minimal' for counts, 'compact' (default) for flagged packages, 'full' for all details.
  • list_package_statsList statistics about loaded package lists for hallucination detection
  • scan_agent_promptScan a prompt for malicious intent. Returns BLOCK/WARN/LOG/ALLOW. Use verbosity='minimal' for action only, 'compact' (default) for findings, 'full' for audit details.
  • scan_git_diffScan git diff for new security vulnerabilities. Only reports issues on changed lines. Use for PR reviews.
  • scan_projectScan an entire directory for security vulnerabilities with .gitignore support and security grading. Use verbosity='minimal' for grade + counts, 'compact' (default) for top issues, 'full' for all details.
  • scan_agent_actionPre-execution security check for agent actions (bash, file_write, file_read, http_request, file_delete, cron, process_spawn, git, docker). Returns ALLOW/WARN/BLOCK.
  • scan_mcp_serverScan an MCP server's source code for security vulnerabilities: overly broad permissions, missing input validation, data exfiltration, insecure patterns. Returns grade (A-F) and recommendations.
  • +11 more on 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.

Agent Security Scanner MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "agent-security-scanner-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "agent-security-scanner-mcp"
      ]
    }
  }
}

Supply Chain Guard

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

Frequently asked questions

Agent Security Scanner MCP is categorized under Security and uses a local stdio subprocess. Supply Chain Guard belongs to Security and uses a local stdio subprocess. Pick Agent Security Scanner MCP 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.

Agent Security Scanner MCP has no declared pricing — check the project's own site. 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 agent-security-scanner-mcp and supply-chain-guard as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Agent Security Scanner MCP has a quality signal of 68/100 (Great) with 2 views, 0 installs and 124 GitHub stars. Supply Chain Guard has 51/100 (Good) with 4 views, 0 installs and 7 GitHub stars.