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.
npx agentmods add mcp/libr3andr3/lucidmem/lucidmemgit clone --depth 1 https://github.com/libr3andr3/lucidmemWrote 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/libr3andr3/lucidmem/lucidmem)<a href="https://agentmods.dev/mcp/libr3andr3/lucidmem/lucidmem"><img src="https://agentmods.dev/badge/mcp/libr3andr3/lucidmem/lucidmem.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
lucidmem 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 5d 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
{ "lucidmem": { "command": "uvx", "args": [ "lucidmem" ] } }
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.
- 5d ago First seen · 8 lines scan A 312e5be2473b
lucidmem is an MCP server published in the GitHub repository libr3andr3/lucidmem (0 stars, last pushed 1mo 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
brain-v42
MCP server "brain-v42", hosted remotely at 127.0.0.1, as configured in hawkixs/brain-v42.
mb
MCP server for MindBase — query and write to your wiki from Claude Desktop, Cursor, Windsurf, Cline, or any MCP-compatible AI client. Runs locally from the mindbase-mcp npm package.
callosium
One shared memory for every AI you use, in plain Markdown files you own. Runs locally from the callosium npm package. Needs 1 environment variable to run.
memstem
Unified memory and skill infrastructure for AI agents. Runs locally from the memstem Python package.
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.
akb
AKB MCP stdio client — connect any AI agent to AKB knowledge base. Zero dependencies, auto-reconnect. Runs locally from the akb-mcp npm package. Needs 2 environment variables to run.