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/Mediaeater/swarm-at-ledgerWrote 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/mediaeater/swarm-at-ledger/swarm-at)<a href="https://agentmods.dev/mcp/mediaeater/swarm-at-ledger/swarm-at"><img src="https://agentmods.dev/badge/mcp/mediaeater/swarm-at-ledger/swarm-at/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/mediaeater/swarm-at-ledger/swarm-at"><img src="https://agentmods.dev/badge/mcp/mediaeater/swarm-at-ledger/swarm-at.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
swarm-at 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 12d 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-at": { "command": "uvx", "args": [ "swarm-at-sdk", "-m", "swarm_at.mcp" ], "env": { "SWARM_API_URL": "", "SWARM_API_KEY": "" } } }
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.
- 12d ago First seen · 14 lines scan A ce9537795d97
swarm-at is an MCP server published in the GitHub repository Mediaeater/swarm-at-ledger (1 stars, last pushed 6mo 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-evidence-ledger
MCP server "mcp-evidence-ledger" as configured in brianpelow/mcp-evidence-ledger. Runs locally from the mcp-evidence-ledger Python package.
agentseal
Verifiable action logs for AI agents. Every action is recorded in a SHA-256 hash chain. Runs locally from the agentseal-mcp npm package. Needs 1 environment variable to run.
org-as-code
MCP server "org-as-code" as configured in SYNTRIAD/org-as-code. Runs locally from the org-as-code Python package.
bernstein
MCP server "bernstein" as configured in sipyourdrink-ltd/bernstein. Launched with bernstein mcp.
termlink
MCP server "termlink" as configured in DimitriGeelen/agentic-engineering-framework. Launched with termlink mcp serve. Needs 1 environment variable to run.
fw
MCP server "fw" as configured in DimitriGeelen/agentic-engineering-framework. Runs agents/mcp/framework_mcp_server.py with python3.