agent-bom

Name: agent-bom
Author: koda-ai-studio

by koda-ai-studioversion 0.113.2i★ –iComputer or cloud

Registry nameio.github.koda-ai-studio/agent-bom

Install

Overview

Description from the maker (original English)

AI supply-chain BOM: agents, MCP servers, packages and recorded reach. Scan and investigate via MCP.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi3 of 3 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Computer or cloud
Transport: stdio, Streamable HTTP
Category: Other
You need to fill in: NVD_API_KEY, Authorization

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 3 of 3 passed
Runs on the maker’s server: what you ask it goes through their server.
You fill in yourself: NVD_API_KEY, Authorization

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

Runs in the cloudNothing to install; it connects over the internet
PyPIPython’s uv installed (for the uvx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.

Or run it on your computer

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "agent-bom": {
      "command": "uvx",
      "args": [
        "agent-bom",
        "mcp",
        "server"
      ],
      "env": {
        "NVD_API_KEY": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add --transport http agent-bom https://agent-bom-mcp.up.railway.app/mcp --header 'Authorization: your-value'

Or run it on your computer

claude mcp add agent-bom --env NVD_API_KEY=your-value -- uvx agent-bom mcp server

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "agent-bom": {
      "url": "https://agent-bom-mcp.up.railway.app/mcp",
      "headers": {
        "Authorization": "your-value"
      }
    }
  }
}

Or run it on your computer

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "agent-bom": {
      "command": "uvx",
      "args": [
        "agent-bom",
        "mcp",
        "server"
      ],
      "env": {
        "NVD_API_KEY": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "agent-bom": {
      "type": "http",
      "url": "https://agent-bom-mcp.up.railway.app/mcp",
      "headers": {
        "Authorization": "your-value"
      }
    }
  }
}

Or run it on your computer

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "agent-bom": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "agent-bom",
        "mcp",
        "server"
      ],
      "env": {
        "NVD_API_KEY": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

NVD_API_KEY secret env
NVD API key for higher rate limits on vulnerability enrichment
Authorization secret HTTP header
Optional. Without it, only the read-only lookup tools (check, intel_lookup) answer. A deployment bearer token unlocks the rest.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

The server asks you to sign in before it lists its tools.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account koda-ai-studio, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
✓ Pass
Endpoint responds
Responded in 133 ms (HTTP 401)
✓ Pass
Sign-in with OAuth
Declares OAuth sign-in, so your AI app can take you to log in
… Not checked yet
No hidden instructions in tool descriptions
Not checked yet; we read the tool list when we check the endpoint

Compared with others in Otheri

More stars than 0% of the other 18386 servers in this category
Published to the registry more recently than 92% of the other 18386 servers in this category
Basic checks equal to or better than 100% of the other 18386 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is agent-bom safe?

It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: NVD_API_KEY, Authorization

Does it run on my computer or in the cloud?

Either way works: install it on your computer or connect to the cloud version.

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.113.2) reached the registry 3 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, Tethered Trust

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated 2 days ago

Install

Tethered Trust

by tetheredtrust.com

Fit, compatibility and recall checks for AI agents before they buy: verdicts, evidence, receipts.

Runs in the cloudUpdated today

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

AI supply-chain BOM: every agent, MCP server and AI package, and what each one can reach.

For AppSec teams and developers who run Claude Code, Cursor, Codex or any MCP client: see which agents, MCP servers, tools and packages are installed, which are vulnerable, and what each one can reach. Local scans need no account.

Quick start · Try in browser · Laptop → team → org · What you get · Product tour · Docs

Quick start

From the repository you want to inspect, with uv installed:

uvx agent-bom scan . --no-discover -f html -o agent-bom-report.html

Open agent-bom-report.html for inventory, findings and fix guidance. Run the same scan again later and agent-bom prints what changed since the last one. No MCP configuration in the project? Package findings still apply. No project handy? Run uvx agent-bom scan --demo --offline for a bundled sample; Exit 1 is expected there because the sample trips the security gate. A non-zero exit can mean a security gate or incomplete assessment; inspect the report and coverage (exit codes, what a scan does and does not establish, first-run guide).

From laptop to team to org

Where	Start with	You get
On your laptop	`uvx agent-bom scan .` · `claude mcp add agent-bom -- uvx agent-bom mcp server`	Findings with fixes, a delta on every rescan, and agent-bom as a tool inside your coding agent (MCP server, plugins)
In your team	`uses: koda-ai-studio/agent-bom@v0` on pull requests and a weekly `schedule:`	A PR gate with a findings comment and SARIF in code scanning, plus a weekly rescan that catches new CVEs in unchanged code (GitHub Action)
Across your org	`agent-bom up` locally, then Docker Compose or the Helm chart from `oci://ghcr.io/koda-ai-studio/charts/agent-bom`	Retained scans, one graph of agents, MCP servers, packages and credentials, SSO and audit, in your own infrastructure (self-host)

Why an AI supply-chain BOM

Agents and MCP servers ship without an inventory. A CVE in an AI package, a poisoned tool description or an over-scoped credential matters by what the agent that loads it can reach. A package SBOM stops at packages; agent-bom records the chain and keeps the evidence for every edge.

1. Inventory	2. Correlate	3. Act
Agents, MCP servers, tools, packages, models, credential references and cloud resources, read-only	One graph: agent → MCP server → tool → package → credential → data, each edge with its source	Fix, gate CI, block poisoned tool calls, rescan to verify

*Fictional sample estate. Dashed use, credential and access links are configured or modeled, not observed at runtime; path analysis covers the collected snapshot only. The AWS badge describes environment membership; these sample agents have no recorded execution host or model endpoint.* Agent, hosting and model context.

Findings map to OWASP LLM Top 10, OWASP Agentic Top 10, OWASP MCP Top 10, MITRE ATLAS, EU AI Act and NIST AI RMF; control mappings are investigation context, not certification.

What you get

Start with the workflow you need. An individual developer can scan, inspect findings and verify fixes without a shared control plane or a compliance workflow. Teams can add retained scans and shared inventory; organizations can add identity, audit review and governance when needed. These are adoption paths, not separate editions or permissions. See the deployment chooser.

Offering	What it includes	Cost	Start
CLI, CI and exports	Local and CI scans; SARIF, CycloneDX, SPDX, JSON and HTML exports; `check` pre-install gate; GitHub Action	Free, Apache-2.0; no account	First run
Self-hosted control plane	API and dashboard on Compose or Helm with PostgreSQL, SSO/OIDC, roles, tenant isolation, audit chain, lake evidence import and executive briefs	Free, Apache-2.0; your infrastructure	Self-host · Helm
MCP server and agent plugins	`agent-bom mcp server` tool profiles; Claude Code and Codex plugins; OpenClaw and Cortex Code skills	Free; runs locally	MCP server · Plugins
Hosted service and support	No managed cloud offering today. Community support on GitHub; security reports follow published response targets, not a contractual SLA	—	Product boundaries · Support model

What it covers

Area	What you get
AI agents and MCP	Agents, MCP servers, tools and credentials from local configs and agent frameworks, linked to what they can reach.
Models and AI platforms	Supported OpenAI, Hugging Face, Ollama, MLflow and W&B assets, with available model provenance beside dependencies and agent context.
Runtime	An MCP proxy and gateway that alert on poisoned tools and injected results, or block them with `--injection-mode enforce`.
SBOM, AI-BOM and Agent-BOM	Software SBOMs in CycloneDX or SPDX. CycloneDX AI components carry collected model metadata. Native agent-bom JSON connects agents, MCP servers, tools, credential references and packages.
Dependencies	Lockfiles and manifests across Python, JavaScript, Go, Java, .NET, Rust and more, matched against OSV, GitHub advisories and NVD with KEV and EPSS.
Code	Findings imported from any SARIF producer, plus native analysis of AI code (prompt-injection sinks, guardrails, tool exposure) and whether your code reaches the vulnerable function.
Containers and IaC	Images scanned in bounded memory and time; Dockerfile, Terraform, Kubernetes, Helm and compose risks with exact lines in SARIF.
Cloud and data platforms	Read-only collection from AWS, Azure, GCP, Kubernetes, Databricks and Snowflake, with provider-specific posture checks and graph context. Per-lane rule counts are generated from code in the capability matrix.
GPU and AI infrastructure	AI workloads on CoreWeave, Nebius, Lambda, RunPod, Vast.ai and Crusoe; GPU containers and Kubernetes GPU nodes. Collection depth varies by provider.

Generate a BOM from a project, or inspect an agent inventory with sample data:

agent-bom scan --project . -f cyclonedx -o sbom.cdx.json

agent-bom scan --project . -f spdx -o sbom.spdx.json agent-bom scan --demo --offline -f json -o agent-bom.json

Model metadata appears when the source supplies it. A BOM is an inventory, not proof of safe execution or complete collection.

All supported sources and evidence destinations, by category

Area	Integrations
AI clients + IDEs	Claude, Codex, Cursor, GitHub Copilot, Windsurf, Cortex Code, Gemini CLI, JetBrains AI, Junie, Amazon Q, Cline, Roo Code, Continue, Zed, Goose, Snowflake CLI, Docker MCP Toolkit, Tabnine, Sourcegraph Cody, Aider, Void, Aide, Trae, Pieces, OpenClaw, mcp-cli
AI platforms + model hubs	OpenAI, Hugging Face, Ollama, MLflow, W&B, Langfuse, LangSmith
GPU + neo clouds	CoreWeave, Nebius, Lambda, RunPod, Vast.ai, Crusoe, GPU containers + K8s GPU nodes
Hyperscalers + Kubernetes	AWS, Azure, GCP, Kubernetes
Data + vector stores	Snowflake, Databricks, Supabase, Pinecone, Qdrant, Weaviate, Chroma, Milvus
Identity + SaaS + dev	Okta, GitHub Actions, Vercel, Microsoft Entra ID, Jira, ServiceNow, Slack, Jamf
Evidence out	ClickHouse, BigQuery, S3, GCS, Azure Blob, Jira tickets, Slack alerts, Vanta, Drata, OCSF syslog

Product names and logos are trademarks of their owners, used only to identify supported evidence sources. Their use does not imply endorsement or partnership.

Investigate context and exposure

Which agent uses the vulnerable component? What could it reach? What evidence supports that path? Correlate retained scans by exact, tenant-scoped identities and trace the recorded blast radius from each agent through its MCP servers to packages, findings, credentials and data stores. Each relationship keeps its source and evidence kind. Agent kind, platform, execution host and model links are separate facts: an environment badge does not say where an agent runs.

From agent to verified fix: select Document Intake Agent → inspect CVE-2023-4863 (high, KEV-listed) and the evidence on each arrow → take the proposed remediation → rescan the changed pin and compare snapshots. The comparison verifies the changed input, not a running deployment.

Am I affected by a new CVE? Match it against stored scans, including CVEs only NVD has published. You get affected assets with their patch target, possibly affected distro packages to verify, and the blast radius (walkthrough):

agent-bom db update                                   # refresh OSV, NVD, KEV and EPSS

agent-bom db advisory

Only the beginning is shown; read the rest in the repo

agent-bom

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Or run it on your computer

Or run it on your computer

Or run it on your computer

Or run it on your computer

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

Tethered Trust

README from the maker

Quick start

From laptop to team to org

Why an AI supply-chain BOM

What you get

What it covers

Investigate context and exposure