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/xbrxr03/memorygraphWrote 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/xbrxr03/memorygraph/memorygraph-agent)<a href="https://agentmods.dev/mcp/xbrxr03/memorygraph/memorygraph-agent"><img src="https://agentmods.dev/badge/mcp/xbrxr03/memorygraph/memorygraph-agent/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/xbrxr03/memorygraph/memorygraph-agent"><img src="https://agentmods.dev/badge/mcp/xbrxr03/memorygraph/memorygraph-agent.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
memorygraph-agent 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
{ "memorygraph-agent": { "command": "uvx", "args": [ "memorygraph-agent" ] } }
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 8c1b63aa19f8
memorygraph-agent is an MCP server published in the GitHub repository xbrxr03/memorygraph (0 stars, last pushed 1mo ago), 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-31.
Other mcp servers, from other repositories
memex
Temporal engineering context for agents via MCP. Runs locally from the stifler-memex-mcp npm package. Needs 4 environment variables to run.
mapi-agent-memory
MCP server "mapi-agent-memory" as configured in cabo0m/mapi-agent-memory. Runs locally from the mapi-agent-memory Python package.
agent-handoff-memory
MCP server "agent-handoff-memory" as configured in JusticeUA/agent-handoff-memory. Runs locally from the agent-handoff-memory npm package.
kernal-mcp
Graph-native memory for AI agents: a knowledge graph built from conversation, via MCP. Runs locally from the kernal-mcp npm package.
orenyl-mcp-server
Production-minded governed memory MCP server for AI agents with deterministic deletion and auditable lineage. Runs locally from the orenyl-mcp-server Python package.
ori-memory
Persistent memory infrastructure for AI agents. Identity, knowledge graph, and search. Runs locally from the ori-memory npm package.