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/rstreamlabs/rstream-goWrote 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/rstreamlabs/rstream-go/rstream)<a href="https://agentmods.dev/mcp/rstreamlabs/rstream-go/rstream"><img src="https://agentmods.dev/badge/mcp/rstreamlabs/rstream-go/rstream/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/rstreamlabs/rstream-go/rstream"><img src="https://agentmods.dev/badge/mcp/rstreamlabs/rstream-go/rstream.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
rstream 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 22d 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
{
"rstream": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"docker.io/rstream/rstream:1.32.4"
],
"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.
- 22d ago Changed b96b782066a2
- 1mo ago Changed 80fd84c88f38
- 1mo ago First seen · 12 lines scan A a0b83c4f5bd0
rstream is an MCP server published in the GitHub repository rstreamlabs/rstream-go (1 stars, last pushed yesterday), 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
homebutler
Tells an agent what changed on a server since it last looked - status, Docker, backups, Proxmox. Runs locally from the homebutler npm package.
stockbit-mcp
Indonesian exchange (IDX) via your own Stockbit account: quotes, bandarmology, charts. Unofficial. Runs locally from the stockbit-mcp npm package. Needs 4 environment variables to run.
gopls-mcp
gopls, the Go language server, exposed as an MCP server: lets the agent query symbols, definitions, references and diagnostics in a Go codebase. Launched with ./scripts/run.sh.
pipefy
MCP server "pipefy", hosted remotely at mcp.pipefy.com, as configured in pipefy/ai-toolkit.
memi
Memi is the read-only design engineering audit and skill layer for coding agents. Runs locally from the @memi-design/cli npm package.
cc-audit
MCP server "cc-audit" as configured in ryo-ebata/cc-audit. Launched with ./target/release/cc-audit serve.