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/velixarai/velixar-mcp-server/memorygit clone --depth 1 https://github.com/VelixarAi/velixar-mcp-serverWrote 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/velixarai/velixar-mcp-server/memory)<a href="https://agentmods.dev/mcp/velixarai/velixar-mcp-server/memory"><img src="https://agentmods.dev/badge/mcp/velixarai/velixar-mcp-server/memory.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
memory 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
{
"memory": {
"command": "npx",
"args": [
"-y",
"velixar-mcp-server"
],
"env": {
"VELIXAR_API_KEY": ""
}
}
}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 · 12 lines scan A 1ae0f0f3e0aa
memory is an MCP server published in the GitHub repository VelixarAi/velixar-mcp-server (1 stars, last pushed 4d 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
deerdawn
AI session memory: the brief your AI reads before every session so no session starts cold. Runs locally from the @deerdawn/mcp-server npm package. Needs 1 environment variable to run.
mcp
AI memory layer — one shared, persistent memory across every AI tool you connect. Remote server at mcp.atlaso.ai.
honcho
Memory that reasons: continual learning for stateful agents. Better context, fewer tokens. Remote server at mcp.honcho.dev.
plur
Open, local-first engram memory for AI agents: read, correct, delete; shared over MCP. Runs locally from the @plur-ai/mcp npm package.
pmb-ai
PMB (Personal Memory Brain) - local-first persistent memory for AI coding agents (MCP server, fully offline, no API keys). Runs locally from the pmb-ai Python package.
ori-memory
Persistent memory infrastructure for AI agents. Identity, knowledge graph, and search. Runs locally from the ori-memory npm package.