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.
Open security platform for agentic infrastructure — broad scanning, blast radius, runtime, and trust
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.
This server is missing a description. Tools and install config are also missing.If you've used it, help the community.
Add informationBe 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
An evil MCP server used for redteam testing
Yunxiao MCP Server provides AI assistants with the ability to interact with the Yunxiao platform. It provides a set of tools that interact with Yunxiao's API, allowing AI assistants to manage Codeup repository, Project, Pipeline, Packages etc.
Enhanced MCP server for GitLab: group projects listing and activity tracking
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.
Open security scanner and self-hosted control plane for AI/MCP infrastructure.
Headless agent primitives and human cockpit surfaces over the same evidence model.
Docs · First Run · Self-host · GitHub Action · Docker · Changelog
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.
pip install agent-bom
agent-bom quickstart --dry-run --offline # print the onboarding plan
agent-bom quickstart --run --offline # write sample, scan, seed gateway policy, populate the cockpit
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.