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/VineetV2/peon-memWrote 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/vineetv2/peon-mem/peon-mem)<a href="https://agentmods.dev/mcp/vineetv2/peon-mem/peon-mem"><img src="https://agentmods.dev/badge/mcp/vineetv2/peon-mem/peon-mem.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
peon-mem 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
{
"peon-mem": {
"command": "npx",
"args": [
"-y",
"peon-mem"
],
"env": {
"PEON_DAEMON_URL": "http://127.0.0.1:3737"
}
}
}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 · 12 lines scan A c90a9f2ce9aa
peon-mem is an MCP server published in the GitHub repository VineetV2/peon-mem (2 stars, last pushed 6d 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
plur
Open, local-first engram memory for AI agents: read, correct, delete; shared over MCP. Runs locally from the @plur-ai/mcp npm package.
homestead-memory
Verifiable, local-first AI memory that catches rot, tampering, and poisoning. Plain markdown you own. Runs locally from the homestead-memory Python package.
epiphany
One private, local memory your AI tools share. Cross-model, on-device, never lose a session. Runs locally from the epiphany-mcp npm package.
honcho
Memory that reasons: continual learning for stateful agents. Better context, fewer tokens. Remote server at mcp.honcho.dev.
remnic
MCP server "remnic", hosted remotely at localhost, as configured in joshuaswarren/remnic.
ori-memory
Persistent memory infrastructure for AI agents. Identity, knowledge graph, and search. Runs locally from the ori-memory npm package.