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/lionellau/leptinWrote 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/lionellau/leptin/leptin-hlp)<a href="https://agentmods.dev/mcp/lionellau/leptin/leptin-hlp"><img src="https://agentmods.dev/badge/mcp/lionellau/leptin/leptin-hlp/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/lionellau/leptin/leptin-hlp"><img src="https://agentmods.dev/badge/mcp/lionellau/leptin/leptin-hlp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
leptin-hlp 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 8d 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
{ "leptin-hlp": { "command": "uvx", "args": [ "leptin-hlp" ] } }
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.
- 8d ago First seen · 8 lines scan A fb6402bd3a13
leptin-hlp is an MCP server published in the GitHub repository lionellau/leptin (0 stars, last pushed 2mo 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
memshelf-mcp
Working-memory shelf for AI agents — offload closed topics to a docshelf shelf as digest-indexed episodes, recall by index. Runs locally from the memshelf-mcp Python package.
session-migrator
MCP server "session-migrator" as configured in liangyuan0219/session-migrator. Runs locally from the session-migrator Python package.
thor
MCP server "thor" as configured in nworks3d/THOR-memory-bible-for-AI. Runs in Docker (ghcr.io/nworks3d/thor-mcp:2.1.1).
palinode
MCP server "palinode" as configured in phasespace-labs/palinode. Launched with palinode-mcp.
mcp-pve
Manage Proxmox VE through AI assistants. Runs locally from the @samik081/mcp-pve npm package. Needs 3 environment variables to run.
memex
Temporal engineering context for agents via MCP. Runs locally from the stifler-memex-mcp npm package. Needs 4 environment variables to run.