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/trinity-tick/trinity/trinity-memorygit clone --depth 1 https://github.com/trinity-tick/trinityGrade A, and why
trinity-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 yesterday.
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
{
"trinity-memory": {
"command": "uvx",
"args": [
"trinity-memory"
],
"env": {}
}
}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.
- yesterday First seen · 9 lines scan A 071778ba5c5d
trinity-memory is an MCP server published in the GitHub repository trinity-tick/trinity (1 stars, last pushed 3d 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
memx
MCP server "memx" as configured in NeoLi00/memX. Runs ${CLAUDE_PLUGIN_ROOT}/dist/.runtime/src/bin/memx-mcp.mjs with node. Needs 3 environment variables to run.
pensyve
MCP server "pensyve", hosted remotely at mcp.pensyve.com, as configured in major7apps/pensyve.
pensyve
Universal memory runtime for AI agents — episodic, semantic, and procedural memory. Remote server at mcp.pensyve.com.
mnemic-memory
MCP server "mnemic-memory" as configured in dongtang3/mnemic. Launched with /bin/bash ./scripts/run-agent-memory-mcp.sh. Needs 1 environment variable to run.
mnesio
MCP server "mnesio" as configured in mnesio/mnesio. Launched with mnesio-mcp. Needs 2 environment variables to run.
ori-memory
Persistent memory infrastructure for AI agents. Identity, knowledge graph, and search. Runs locally from the ori-memory npm package.