Skip to main content
Glama

What it is

agent-bom scans repositories, images, and cloud accounts, then correlates what it finds into one Finding + UnifiedGraph model — powering CLI and CI artifacts, fleet and browser investigations, compliance evidence, and runtime policy. Run the scanner without an account, or deploy the control plane inside your own cloud, VPC, cluster, database, identity, and audit boundary.

Graph provenance stays explicit: collected, inferred, static, and runtime relationships remain distinct, and unavailable evidence is never upgraded to observed.

Related MCP server: agent-audit

Who it is for

Role

Start here

Primary outcome

AI engineer

agent-bom scan .

Inventory agents, MCP servers, and models, and catch issues before they ship

Security engineer

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

Investigate exposure paths, identities, and evidence provenance

GRC / audit

agent-bom report compliance-narrative scan.json

Review control mappings and export evidence with explicit gaps

Leadership / CISO

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

Review posture, coverage, material risk, and change over time

Security engineering and GRC remain separate workflows: findings and reachability are not presented as audit certification. See product boundaries.

The gallery uses deterministic sample data, visibly labeled in the UI. It is product-state proof, not customer or advisory evidence.

Overview

Findings

Investigation

Remediation

Cloud and environment lineage

Agent mesh

Capture protocol

Quick start

Run against the repository in your current directory:

pip install agent-bom
agent-bom scan .

The console shows inventory, findings, and reachable impact. Save an artifact with agent-bom scan . -f sarif -o findings.sarif, or follow the first-run guide for exit codes, formats, and CI use.

Use the curated, explicitly synthetic sample when you only want to inspect the output shape:

agent-bom scan --demo --offline

The sample intentionally contains blocking findings, so exit status 1 is expected.

Self-host

Start the loopback control plane:

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

For a shared deployment, use the documented Docker or Helm path and configure real identity, TLS, PostgreSQL, encryption, and audit keys before exposing it.

Target

Start here

Docker Compose

Platform compose — PostgreSQL, split secrets, migration job

Docker Compose (evaluation)

Pilot compose — loopback only, SQLite, no auth

Helm / Kubernetes

helm install agent-bom oci://ghcr.io/msaad00/charts/agent-bom --version 0.99.0

EKS

Terraform module

Snowflake SPCS / Native App

scripts/deploy/install.sh snowflake-native · install guide

Air-gapped

Image bundle guide

Examples target this release candidate; confirm release availability before copying an exact pin. Otherwise, use the latest version shown on PyPI.

Deployment overview · Enterprise configuration · Cloud connections

Need

First action

Artifact or next step

GitHub CI

uses: msaad00/agent-bom@v0.99.0

SARIF, PR summary, and a policy exit code

Cloud evidence

agent-bom connect aws

Stored connection reference; run scans from the control plane

Runtime gateway

agent-bom gateway serve --from-control-plane http://127.0.0.1:8422 --bind 127.0.0.1:8090

Allow, warn, and block audit events

Agent interface

agent-bom mcp server

77 MCP tools, 6 resources, and 8 workflow prompts

Agent distribution

Smithery manifest · Glama · MCP registry · Docker MCP

Registry-specific installation metadata

MCP server mode exposes 77 MCP tools, 6 resources, and 8 workflow prompts, all read-first: discovery and analysis never mutate a scanned target.

The CLI, Docker, API, Helm chart, MCP server, gateway, and SDK are distribution surfaces of the same product. The Snowflake SPCS / Native App lane runs inside the customer's Snowflake account; it is a customer-owned deployment target, not an agent-bom-hosted service. Snowflake and Snowpark also remain connector and runtime integrations for the other deployment profiles.

Surface

Get it

Python package

pip install agent-bomPyPI

Container

docker pull agentbom/agent-bomDocker Hub

Kubernetes

helm install agent-bom oci://ghcr.io/msaad00/charts/agent-bom

GitHub Action

msaad00/agent-bom

MCP server

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

MCP registries

Smithery manifest · Glama · MCP registry · Docker MCP

SDKs

Python · TypeScript · Go

Trust

  • Read-only discovery by default; runtime write decisions are separate and explicit.

  • Credentials are write-only where stored, encrypted at rest, and never returned by API responses.

  • API and control-plane routes are tenant scoped and auth protected outside explicit local mode.

  • Missing evidence is shown as unavailable or partial, never converted into a factual zero.

  • Public examples and screenshots use deterministic synthetic identifiers only.

Threat model · Release verification · Security policy · MCP security model

Contributing

Start with CONTRIBUTING.md, AGENTS.md, and the open issues.

Apache-2.0 licensed.

Install Server
A
license - permissive license
A
quality
A
maintenance

Maintenance

Maintainers
16hResponse time
1dRelease cycle
134Releases (12mo)
Issues opened vs closed

Related MCP Servers

  • A
    license
    A
    quality
    D
    maintenance
    A security scanner that evaluates installed MCP servers for vulnerabilities by aggregating findings from 16 scanning engines into detailed trust scores. It enables users to scan their local AI agent configurations or specific repository URLs for potential security risks.
    4
    2
    Apache 2.0
  • A
    license
    -
    quality
    C
    maintenance
    Security scanner for MCP servers. Detects prompt injection, command injection, auth bypass, and excessive permissions across tools, resources, and prompts.
    26
    2
    MIT

View all related MCP servers

Related MCP Connectors

  • Security scanner for MCP servers. Detect vulnerabilities, prompt injection, and tool poisoning.

  • Zero-config MCP security scanner for AI-generated apps. 25K+ vulnerability patterns.

  • Scans MCP servers for tool poisoning, prompt injection and supply chain risks.

View all MCP Connectors

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