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/Volpestyle/swarm-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/volpestyle/swarm-mcp/swarm-mcp)<a href="https://agentmods.dev/mcp/volpestyle/swarm-mcp/swarm-mcp"><img src="https://agentmods.dev/badge/mcp/volpestyle/swarm-mcp/swarm-mcp/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/volpestyle/swarm-mcp/swarm-mcp"><img src="https://agentmods.dev/badge/mcp/volpestyle/swarm-mcp/swarm-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
swarm-mcp 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 10d 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
{ "swarm-mcp": { "command": "npx", "args": [ "-y", "swarm-mcp" ] } }
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.
- 10d ago First seen · 9 lines scan A 4c58015ca63b
swarm-mcp is an MCP server published in the GitHub repository Volpestyle/swarm-mcp (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
nutrition-mcp
Personal nutrition tracking — log meals, track macros, review history, import from another app. Remote server at nutrition-mcp.com.
bitcoin-mcp
MCP server for Bitcoin — 49 tools for AI agents to save money on fees. Zero config, works out of the box. Runs locally from the bitcoin-mcp Python package. Needs 5 environment variables to run.
regen-compute
Regenerative AI — fund verified ecological regeneration from your AI sessions via Regen Network. Estimate your footprint, browse carbon and biodiversity credits, and retire them on-chain via credit card. Runs locally from the regen-compute npm package.
sui-mcp
Read-only Sui blockchain analytics: 59 tools, protocol-aware tx decoding, no API keys or wallet. Runs locally from the sui-analytics-mcp npm package. Needs 6 environment variables to run.
causallayer-mcp
Deterministic AI-liability attribution: signed, Bitcoin-anchored vendor/deployer/user fault split. Remote server at causallayer-mcp-demo.zykm9qkk7j.workers.dev.
openstates-mcp-server
Search bills, legislators, committees, and events across all 50 US states, DC, and 5 US territories. Runs locally from the @cyanheads/openstates-mcp-server npm package. Needs 5 environment variables to run.