Skip to content

agent-bom scan

Verified

Security scanner for AI infrastructure — discovers MCP clients and servers, checks packages for CVEs (OSV, NVD, EPSS, KEV), maps blast radius, and generates...

84 downloads
$ Add to .claude/skills/

About This Skill

# agent-bom-scan — AI Supply Chain Vulnerability Scanner

Discovers MCP clients and servers across 22 AI tools, checks packages for CVEs, maps blast radius, and generates remediation plans.

Install

```bash pipx install agent-bom agent-bom scan # auto-discover + scan agent-bom check langchain # check a specific package agent-bom where # show all discovery paths ```

As an MCP Server

```json { "mcpServers": { "agent-bom": { "command": "uvx", "args": ["agent-bom", "mcp"] } } } ```

Tools (8)

| Tool | Description | |------|-------------| | `scan` | Full discovery + vulnerability scan pipeline | | `check` | Check a package for CVEs (OSV, NVD, EPSS, KEV) | | `blast_radius` | Map CVE impact chain across agents, servers, credentials | | `remediate` | Prioritized remediation plan for vulnerabilities | | `verify` | Package integrity + SLSA provenance check | | `diff` | Compare two scan reports (new/resolved/persistent) | | `where` | Show MCP client config discovery paths | | `inventory` | List discovered agents, servers, packages |

Example Workflows

``` # Check a package before installing check(package="@modelcontextprotocol/server-filesystem", ecosystem="npm")

# Map blast radius of a CVE blast_radius(cve_id="CVE-2024-21538")

# Full scan scan() ```

Privacy & Data Handling

This skill installs agent-bom from PyPI. **Verify the redaction behavior before running with any config files:**

```bash # Step 1: Install pip install agent-bom

# Step 2: Review redaction logic BEFORE scanning # sanitize_env_vars() replaces ALL env var values with *REDACTED* # BEFORE any config data is processed or stored: # https://github.com/msaad00/agent-bom/blob/main/src/agent_bom/security.py#L159

# Step 3: Review config parsing — only structural data extracted: # https://github.com/msaad00/agent-bom/blob/main/src/agent_bom/discovery/__init__.py

# Step 4: Verify package provenance (Sigstore) agent-bom verify agent-bom

# Step 5: Only then run scans agent-bom scan ```

What is extracted: Server names, commands, args, and URLs from MCP client config files across 22 AI tools. What is NOT extracted: Env var values are replaced with `*REDACTED*` by `sanitize_env_vars()` before any processing. Only public package names and CVE IDs are sent to vulnerability databases.

Verification

Use Cases

  • Discover MCP clients and servers installed across 22 AI tools automatically
  • Scan AI agent dependencies for known CVE vulnerabilities
  • Map blast radius of vulnerable packages across the agent ecosystem
  • Generate remediation plans for discovered supply chain vulnerabilities
  • Check specific packages for security issues before adding them to a project

Pros & Cons

Pros

  • +Auto-discovers installations across 22 AI tools — no manual inventory needed
  • +Maps blast radius to understand the impact scope of each vulnerability
  • +Generates actionable remediation plans, not just vulnerability lists

Cons

  • -Scan coverage is limited to known AI tool installation patterns
  • -CVE database freshness depends on update frequency of the underlying data source
  • -Does not fix vulnerabilities — remediation must be done manually

FAQ

What does agent-bom scan do?
Security scanner for AI infrastructure — discovers MCP clients and servers, checks packages for CVEs (OSV, NVD, EPSS, KEV), maps blast radius, and generates...
What platforms support agent-bom scan?
agent-bom scan is available on Claude Code, OpenClaw.
What are the use cases for agent-bom scan?
Discover MCP clients and servers installed across 22 AI tools automatically. Scan AI agent dependencies for known CVE vulnerabilities. Map blast radius of vulnerable packages across the agent ecosystem.

100+ free AI tools

Writing, PDF, image, and developer tools — all in your browser.

Next Step

Use the skill detail page to evaluate fit and install steps. For a direct browser workflow, move into a focused tool route instead of staying in broader support surfaces.