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/Nanda-Kiran/yunaki-memory-mcpWrote 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/nanda-kiran/yunaki-memory-mcp/yunaki-memory-mcp)<a href="https://agentmods.dev/mcp/nanda-kiran/yunaki-memory-mcp/yunaki-memory-mcp"><img src="https://agentmods.dev/badge/mcp/nanda-kiran/yunaki-memory-mcp/yunaki-memory-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/nanda-kiran/yunaki-memory-mcp/yunaki-memory-mcp"><img src="https://agentmods.dev/badge/mcp/nanda-kiran/yunaki-memory-mcp/yunaki-memory-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
yunaki-memory-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 1mo 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
{ "yunaki-memory-mcp": { "command": "npx", "args": [ "-y", "yunaki-memory-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.
- 1mo ago First seen · 9 lines scan A 27873d81f7e0
yunaki-memory-mcp is an MCP server published in the GitHub repository Nanda-Kiran/yunaki-memory-mcp (0 stars, last pushed 19d 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 for AI agents: digest-indexed episodes on a git shelf, recalled a section at a time. Runs locally from the memshelf-mcp Python package.
ai-memory
MCP server "ai-memory" as configured in alphaonedev/ai-memory-mcp. Runs in Docker (ghcr.io/alphaonedev/ai-memory:0.5.1). Needs 1 environment variable to run.
palinode
MCP server "palinode" as configured in phasespace-labs/palinode. Launched with palinode-mcp.
pseudolife-memory
MCP server "pseudolife-memory" as configured in Pseudogiant-xr/Pseudolife-MCP. Launched with C:\path\to\Pseudolife-MCP\.venv\Scripts\pseudolife-mcp.exe. Needs 3 environment variables to run.
obsidian-github-mcp
A permissioned MCP gateway for agent proposals to a Git-backed Obsidian vault. Runs locally from the @sarutobi-sasuke/obsidian-github-mcp npm package. Needs 9 environment variables to run.
memory
MCP server "memory" as configured in Yupcha/memXT. Launched with ${HOME}/.memxt/bin/memxt mcp. Needs 2 environment variables to run.