Skip to main content
Glama

agent-bom scans local and fleet AI infrastructure, builds an AI BOM across agents, MCP servers, tools, packages, credential environment names, cloud, runtime, and skills, then turns that inventory into findings, compliance evidence, and graph-backed exposure paths.

The same evidence is available through CLI/CI, REST API, MCP tools, and a self-hosted dashboard. Runtime proxy/gateway controls are optional and scoped to environments where enforcement is worth the operational cost.

package -> vulnerability finding -> MCP server -> tools + credential refs -> agent

Blast radius is the core idea. A vulnerable package is not just a CVE row; it is linked to the MCP server that loads it, the tools exposed by that server, the credential environment names in reach, and the agents that can call it.

First Run

pip install agent-bom
agent-bom agents --demo --offline

The demo uses real OSV/GHSA advisories against intentionally vulnerable sample packages and produces graph-ready inventory without touching your source tree. For a real local scan:

agent-bom agents -p . -f html -o agent-bom-report.html

Want an inspectable sample stack first?

agent-bom samples first-run
agent-bom agents --inventory agent-bom-first-run/inventory.json -p agent-bom-first-run --enrich

See docs/FIRST_RUN.md for the guided path from CLI output to the dashboard.

Product Proof

The dashboard screenshots below are captured from the packaged UI with bundled demo data, not mockups. The README keeps the first screen focused; expand the gallery when you want to inspect the control-plane surfaces.

Screenshot capture rules and the full manifest live in docs/CAPTURE.md and docs/images/product-screenshots.json.

Start Here

Goal

Command

Artifact

Local agent and MCP inventory

agent-bom agents

findings, AI BOM, graph-ready JSON

Repo and lockfile scan

agent-bom agents -p .

package findings, SARIF/SBOM/HTML when requested

Pre-install guard

agent-bom check flask@2.0.0 --ecosystem pypi

deterministic allow/warn/block result

Container image scan

agent-bom image nginx:latest

image findings and remediation

IaC scan

agent-bom iac Dockerfile k8s/ infra/main.tf

IaC findings and policy context

Cloud posture check

agent-bom cis-benchmark --provider aws

runtime CIS posture evidence

CI gate

uses: msaad00/agent-bom@v0.88.4

SARIF, PR summary, optional code-scanning upload

MCP tools

pip install 'agent-bom[mcp-server]' && agent-bom mcp server

strict-args security tools for MCP clients

Local API/UI

pip install 'agent-bom[ui]' && agent-bom serve

API plus bundled dashboard

Self-hosted pilot

docker compose -f docker-compose.pilot.yml up -d

API and dashboard in your environment

The base wheel is the scanner and CLI path. Optional runtime surfaces fail fast with install hints when their extras are missing.

MCP registry publishing is tracked through the committed Smithery manifest and other registry metadata; install and liveness checks stay in the linked integration docs instead of this front door.

Shipped Surfaces

Surface

Primary user

Current boundary

CLI / CI

developers and release gates

local scans, SARIF/SBOM/HTML/JSON, deterministic exit codes

REST API

control-plane integrations

scans, bulk findings, dataset versions, evaluation runs, graph evidence, audit, runtime summaries

MCP tools

agents and assistants

strict arguments, read-mostly security queries, exposure paths, deploy decisions, audited Shield actions

Dashboard

security teams and operators

inventory, findings, graph cockpit, compliance, evidence, runtime posture

Runtime proxy/gateway

runtime operators

scoped MCP traffic inspection, policy decisions, redacted audit evidence

Python client

services, notebooks, and automation

typed helper for stable REST endpoints in the packaged wheel

TypeScript client

services and agent runtimes

typed helper for stable REST endpoints

MCP server mode advertises 55 MCP tools, 6 resources, and 6 workflow prompts. Most tools are read-only. The three Shield write actions fail closed unless the caller supplies operator_role=admin, operator_scopes=shield:write, and an audit reason.

CLI scan commands run local scan pipelines today. They share lower scanner and discovery libraries with the API, but they are not API wrappers yet.

Deploy In Your Boundary

agent-bom is designed for customer-controlled deployment: local CLI, Docker, GitHub Action, Helm, EKS, Postgres, and optional runtime proxy/gateway.

curl -fsSL https://raw.githubusercontent.com/msaad00/agent-bom/main/deploy/docker-compose.pilot.yml -o docker-compose.pilot.yml
docker compose -f docker-compose.pilot.yml up -d
# Dashboard -> http://localhost:3000

Production self-hosting starts with the deployment chooser:

There is no managed cloud offering in this repository today. Product lane boundaries are documented in docs/PRODUCT_BOUNDARIES.md.

Trust Model

  • Read-only discovery by default for cloud and local inventory.

  • No mandatory telemetry.

  • Credential values are redacted; credential environment names are preserved as evidence so exposure paths stay explainable.

  • Findings can export as JSON, SARIF, CycloneDX, SPDX, Markdown, HTML, and compliance evidence bundles.

  • API and runtime paths are designed for tenant scope, auth boundaries, and audit evidence.

  • OpenAPI artifacts are committed for SDK and client contract checks.

Security and release references:

Product Views

The docs site carries the deployment-oriented walkthroughs behind those screenshots:

Contributing

Contributions are welcome. Start with:

License: Apache-2.0.

Install Server
A
license - permissive license
B
quality
B
maintenance

Maintenance

Maintainers
2dResponse time
0dRelease cycle
110Releases (12mo)
Issues opened vs closed

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/msaad00/agent-bom'

If you have feedback or need assistance with the MCP directory API, please join our Discord server