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/scarletkc/PerennaWrote 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/scarletkc/perenna/perenna-perenna)<a href="https://agentmods.dev/mcp/scarletkc/perenna/perenna-perenna"><img src="https://agentmods.dev/badge/mcp/scarletkc/perenna/perenna-perenna/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/scarletkc/perenna/perenna-perenna"><img src="https://agentmods.dev/badge/mcp/scarletkc/perenna/perenna-perenna.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
perenna 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 11d 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
{
"perenna": {
"command": "uvx",
"args": [
"perenna@latest",
"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.
- 11d ago First seen · 9 lines scan A 2de46db490d0
perenna is an MCP server published in the GitHub repository scarletkc/Perenna (40 stars, last pushed 2d 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-30.
Other mcp servers, from other repositories
membrain
Self-hosted AI memory ledger. You and your agents share one memory store over MCP — one SQLite file, web UI, REST, works offline. Runs locally from the membrain-mcp npm package.
dakera-mcp
MCP server "dakera-mcp" as configured in Dakera-AI/dakera-mcp. Runs in Docker (ghcr.io/dakera-ai/dakera-mcp:0.9.8).
prism-mcp
Persistent session memory for AI coding agents that never leaves your machine — including the on-device model that reasons over it. Restores your prior decisions, open TODOs, and changed files across sessions; adds associative recall of related past work. Runs locally from the prism-mcp-server npm package. Needs 1…
ori-memory
Persistent memory infrastructure for AI agents. Identity, knowledge graph, and search. Runs locally from the ori-memory npm package.
synap
Persistent memory for AI agents — log and recall conversation context over MCP. Remote server at synap-mcp.maximem.ai.
memseek
MCP server "memseek", hosted remotely, as configured in memseekai/memseek.