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/appcreationsca/bumpguard-mcpWrote 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/appcreationsca/bumpguard-mcp/bumpguard)<a href="https://agentmods.dev/mcp/appcreationsca/bumpguard-mcp/bumpguard"><img src="https://agentmods.dev/badge/mcp/appcreationsca/bumpguard-mcp/bumpguard/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/appcreationsca/bumpguard-mcp/bumpguard"><img src="https://agentmods.dev/badge/mcp/appcreationsca/bumpguard-mcp/bumpguard.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
bumpguard 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
{
"bumpguard": {
"command": "uvx",
"args": [
"bumpguard-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 · 9 lines scan A 4705a61775cf
bumpguard is an MCP server published in the GitHub repository appcreationsca/bumpguard-mcp (5 stars, last pushed 4mo ago), licensed MIT. 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
sentry
Lets the agent search and read Sentry issues, errors and traces, and act on them. Runs locally from the @sentry/mcp-server npm package. Needs 1 environment variable to run.
log-essence
Intelligent log analysis for LLMs - extract patterns, redact secrets, compress 50%+. Runs locally from the log-essence Python package.
quellgeist-logs
Model-agnostic AI agent for first-line production-incident triage; read-only evidence tools exposed as MCP servers. Runs locally from the quellgeist Python package. Needs 1 environment variable to run.
quellgeist-metrics
Model-agnostic AI agent for first-line production-incident triage; read-only evidence tools exposed as MCP servers. Runs locally from the quellgeist Python package. Needs 1 environment variable to run.
overllm
Catch the LLM/AI calls you didn't need. A fast, deterministic linter that flags LLM API calls where plain code is simpler, cheaper, and more reliable. Runs locally from the overllm Python package.
lsp-mcp
Universal LSP MCP server. Runs locally from the @theupsider/lsp-mcp npm package.