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/batteryshark/taproomWrote 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/batteryshark/taproom/taproom-cli)<a href="https://agentmods.dev/mcp/batteryshark/taproom/taproom-cli"><img src="https://agentmods.dev/badge/mcp/batteryshark/taproom/taproom-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/batteryshark/taproom/taproom-cli"><img src="https://agentmods.dev/badge/mcp/batteryshark/taproom/taproom-cli.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
taproom-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
{ "taproom-cli": { "command": "npx", "args": [ "-y", "@batteryshark/taproom-cli" ] } }
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 14a4b2e57c06
taproom-cli is an MCP server published in the GitHub repository batteryshark/taproom (1 stars, last pushed 3mo 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
mcp-perplexity-pro
MCP server "mcp-perplexity-pro" as configured in cfdude/mcp-perplexity-pro. Runs locally from the mcp-perplexity-pro Python package.
mcpforge
Generate complete, runnable FastMCP 3.x MCP servers from plain-English descriptions. Runs locally from the fastmcp-builder Python package.
pyautogui-mcp
Expose PyAutoGUI through MCP. Runs locally from the pyautogui-mcp Python package.
obsidian-mcp-guard
MCP server for agent-safe Obsidian vault access with lint validation. Runs locally from the obsidian-mcp-guard Python package.
mcp-document-chat
MCP server "mcp-document-chat" as configured in JuanCamiloMendoza99/mcp-document-chat. Runs locally from the mcp-document-chat Python package.
docs-langchain
MCP server "docs-langchain", hosted remotely at docs.langchain.com, as configured in langchain-ai/langchain.