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/ncz-os/mnemosWrote 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/ncz-os/mnemos/mnemos-core)<a href="https://agentmods.dev/mcp/ncz-os/mnemos/mnemos-core"><img src="https://agentmods.dev/badge/mcp/ncz-os/mnemos/mnemos-core/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/ncz-os/mnemos/mnemos-core"><img src="https://agentmods.dev/badge/mcp/ncz-os/mnemos/mnemos-core.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
mnemos-core 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- uctx — 88% identical, 4 lines differ
What it actually says
{ "mnemos-core": { "command": "uvx", "args": [ "mnemos-core" ] } }
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 · 8 lines scan A e111c395aa60
mnemos-core is an MCP server published in the GitHub repository ncz-os/mnemos (35 stars, last pushed today), 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
akb
Git-backed org memory for AI agents — hybrid search, tables, files & a URI graph over MCP. Runs locally from the akb-mcp npm package. Needs 2 environment variables to run.
tokenknows
TokenKnows MCP server — distill AI coding sessions (Claude Code / Codex / Cursor) into weekly reports, ADRs and a knowledge graph on your self-hosted workbench. Runs locally from the tokenknows-mcp Python package. Needs 5 environment variables to run.
pulse8-ai-cortex-knowledge-vault
PULSE8.ai Cortex — agent-native knowledge OS built on Markdown files. Runs locally from the pulse8-ai-cortex-knowledge-vault Python package. Needs 2 environment variables to run.
secondbrain
Package for secondbrain only! Runs locally from the secondbrain Python package.
mnemos
Memory for agentic AI. Inspired by the brain. Built for the future. Runs locally from the mnemos Python package.
kortex
MCP server "kortex", hosted remotely, as configured in vedantnimbarte/kortex-memory.