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/alexalexalex222/Loop-Factory-mcp-publicWrote 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/alexalexalex222/loop-factory-mcp-public/super-loop-mcp)<a href="https://agentmods.dev/mcp/alexalexalex222/loop-factory-mcp-public/super-loop-mcp"><img src="https://agentmods.dev/badge/mcp/alexalexalex222/loop-factory-mcp-public/super-loop-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/alexalexalex222/loop-factory-mcp-public/super-loop-mcp"><img src="https://agentmods.dev/badge/mcp/alexalexalex222/loop-factory-mcp-public/super-loop-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
super-loop-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
{ "super-loop-mcp": { "command": "npx", "args": [ "-y", "super-loop-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 665e287540f0
super-loop-mcp is an MCP server published in the GitHub repository alexalexalex222/Loop-Factory-mcp-public (0 stars, last pushed 10d 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
novel
MCP server "novel" as configured in Yaemikoreal/OpenNovel. Launched with novel-mcp.
graylog-mcp
Query logs from Graylog: get streams, search messages, aggregate, and get full data. Runs locally from the @jperelli/graylog-mcp npm package. Needs 3 environment variables to run.
fcp-rust
MCP server "fcp-rust" as configured in aetherwing-io/mish. Launched with fcp-rust.
claud-ear
MCP server "claud-ear" as configured in Null-Phnix/claud-ear. Runs locally from the claud-ear Python package.
remnic
MCP server "remnic", hosted remotely at localhost, as configured in joshuaswarren/remnic.
membridge
Cross-platform, cross-process shared memory with rwlock and SPSC ring buffer for Python, powered by Rust. Runs locally from the membridge Python package.