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/standardbeagle/brummerWrote 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/standardbeagle/brummer/brum)<a href="https://agentmods.dev/mcp/standardbeagle/brummer/brum"><img src="https://agentmods.dev/badge/mcp/standardbeagle/brummer/brum/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/standardbeagle/brummer/brum"><img src="https://agentmods.dev/badge/mcp/standardbeagle/brummer/brum.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
brum 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 8261373cb36f
brum is an MCP server published in the GitHub repository standardbeagle/brummer (0 stars, last pushed 2mo ago), with no licence file. 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
memorywhale
MCP server "memorywhale" as configured in wuisabel-gif/MemWhale. Launched with mw-mcp.
agentmap
The TS/JS-accurate repo map for coding agents: ts-morph import/symbol/call graph + MCP query tools. Runs locally from the @raymondchins/agentmap npm package.
sqry
MCP server "sqry" as configured in verivus-oss/sqry. Launched with sqry-mcp --no-daemon. Needs 1 environment variable to run.
prodlint
Production readiness for vibe-coded apps. 52 checks for security, reliability, and performance. Runs locally from the prodlint npm package.
depwire
Dependency graph + 24 MCP tools. Impact analysis, simulation, security, agent coordination. Runs locally from the depwire-cli npm package.
errorlens
Structured error recovery for MCP agents. Runs locally from the mcp-errorlens npm package.