Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/bomly-dev/bomly-cliWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/bomly-dev/bomly-cli/bomly-cli)<a href="https://agentmods.dev/mcp/bomly-dev/bomly-cli/bomly-cli"><img src="https://agentmods.dev/badge/mcp/bomly-dev/bomly-cli/bomly-cli/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/bomly-dev/bomly-cli/bomly-cli"><img src="https://agentmods.dev/badge/mcp/bomly-dev/bomly-cli/bomly-cli.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
bomly-cli scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"bomly-cli": {
"command": "npx",
"args": [
"-y",
"bomly-mcp"
],
"env": {}
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 10 lines scan A cedfa16ffd24
bomly-cli is an MCP server published in the GitHub repository bomly-dev/bomly-cli (14 stars, last pushed today), licensed Apache-2.0. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
pharaoh
MCP proxy for Pharaoh — maps codebases into queryable knowledge graphs for AI agents. Enables Claude Code in headless environments (VPS, SSH, CI) via device flow auth. Runs locally from the @pharaoh-so/mcp npm package.
repo-cartographer
Maps any repo into an architecture diagram (Mermaid/Graphviz) and enforces architecture rules in CI. Runs locally from the repo-cartographer npm package.
matrixscroll
MCP server for signed machine-action records, offline tool-surface checks, with device-agnostic custody and CNSA 2.0 Category 5 crypto (ML-DSA-87, ML-KEM-1024). Runs locally from the matrixscroll Python package.
sswp-mcp
MCP server "sswp-mcp" as configured in VrtxOmega/sswp-mcp. Runs locally from the sswp-mcp npm package.
github-actions
GitHub Actions MCP — view runs, read logs, re-run jobs, and manage CI/CD. Runs locally from the mcp-server-github-actions npm package.
blast-radius-mcp
MCP server "blast-radius-mcp" as configured in tspscale/blast-radius-mcp. Runs locally from the blast-radius-mcp npm package.