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/Leeroo-AI/supermlWrote 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/leeroo-ai/superml/leeroopedia)<a href="https://agentmods.dev/mcp/leeroo-ai/superml/leeroopedia"><img src="https://agentmods.dev/badge/mcp/leeroo-ai/superml/leeroopedia/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/leeroo-ai/superml/leeroopedia"><img src="https://agentmods.dev/badge/mcp/leeroo-ai/superml/leeroopedia.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
leeroopedia 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 9d 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
{
"leeroopedia": {
"type": "http",
"url": "https://mcp.leeroopedia.com/mcp?token=${LEEROOPEDIA_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.
- 9d ago First seen · 6 lines scan A 8bbcc4bdaeb3
leeroopedia is an MCP server published in the GitHub repository Leeroo-AI/superml (195 stars, last pushed 5mo ago), 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-30.
Other mcp servers, from other repositories
dreamd
Local-first, cross-harness memory for AI coding agents. Runs locally from the dreamd-mcp npm package.
contextflux
MCP server "contextflux" as configured in divyanshu-iitian/ContextFlux. Runs locally from the contextflux npm package.
pn-core
MCP server "pn-core" as configured in perniemann/pnCore. Runs packages/pn-core-mcp/dist/index.js with node.
capsule
Compact, source-linked context packs that reduce token waste for coding agents. Runs locally from the capsulectx npm package.
slimdex-mcp
Narrow code retrieval for agents: outlines, symbol context, dep graph, persistent memory. Runs locally from the slimdex-mcp npm package.
agent-relay
MCP server "agent-relay", hosted remotely at localhost, as configured in TsukumoHQ/trovex.