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/gpitrella/memxus-remote-mcp/memxusgit clone --depth 1 https://github.com/gpitrella/memxus-remote-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/gpitrella/memxus-remote-mcp/memxus)<a href="https://agentmods.dev/mcp/gpitrella/memxus-remote-mcp/memxus"><img src="https://agentmods.dev/badge/mcp/gpitrella/memxus-remote-mcp/memxus.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
memxus 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 3d 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.
The source is not reproduced here
Licensed AGPL-3.0
The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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.
- 3d ago First seen · 6 lines scan A b78bb15ba39c
memxus is an MCP server published in the GitHub repository gpitrella/memxus-remote-mcp (3 stars, last pushed 1mo ago), licensed AGPL-3.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-31.
Other mcp servers, from other repositories
rawthink-mcp
Persistent memory MCP server for AI development workflows — hybrid search, knowledge graph, session lifecycle. Runs locally from the rawthink-mcp Python package. Needs 9 environment variables to run.
polypack-mcp
MCP server exposing Polypack as persistent adaptive memory. Runs locally from the polypack-mcp Python package.
penfield-mcp
Persistent memory and knowledge graphs for AI agents. Hybrid search, context checkpoints, and more. Remote server at mcp.penfield.app.
ori-memory
Persistent memory infrastructure for AI agents. Identity, knowledge graph, and search. Runs locally from the ori-memory npm package.
local-memory-mcp
Persistent local AI memory. SQLite + FTS5 + vector search, knowledge graph. No cloud, no API keys. Runs locally from the @studiomeyer/local-memory-mcp npm package. Needs 4 environment variables to run.
synapse-layer
Persistent memory infrastructure for AI agents — AES-256-GCM encrypted at rest, semantic search, MCP-native. Runs locally from the synapse-layer Python package. Needs 3 environment variables to run.