Scan AI/MCP dependencies, descriptor injection, risky tool inputs and authentication configuration.
MCPpedia last refreshed this data
Agent Bom MCP Server is an MCP server that scan AI/MCP dependencies, descriptor injection, risky tool inputs and authentication configuration. Its tool list has not been published yet over stdio and http, requires no API key, and scores 88/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients - only the file and path differ.
{
"mcpServers": {
"agent-bom": {
"args": [
"agent-bom",
"mcp",
"server"
],
"command": "uvx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Scan AI/MCP dependencies, descriptor injection, risky tool inputs and authentication configuration.
Run this in your terminal to verify the server starts. Then let us know if it worked - your result helps other developers.
npx -y '@mcp/server-fs' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories - click any category to see the underlying evidence.
No known CVEs.
Checked @mcp/server-fs against OSV.dev.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience - it helps other developers decide.
Sign in to write a review.
Others in security / devops
MCP server for using the GitLab API
Search-first MCP server for JavaScript reverse engineering: 735 tools across 36 domains.
MCP server for discovering, reading, and changing ZenML resources with compact generic tools
MCP server for 1Password service accounts — tools and resources for vaults and credentials
MCP Security Weekly
Get CVE alerts and security updates for Agent Bom MCP Server and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
AI supply-chain BOM: supported agents, MCP servers and AI packages, 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
From the repository you want to inspect, with uv installed:
uvx agent-bom scan . -f html -o agent-bom-report.html
Open agent-bom-report.html for inventory, findings and fix guidance. The scan
stays inside this repository: packages, MCP configuration, secrets and personal
data, skills and IaC; it does not read agent configuration elsewhere on the machine.
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).

| 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- |