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/ampres-ai/talamusWrote 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/ampres-ai/talamus/talamus-memory-talamus)<a href="https://agentmods.dev/mcp/ampres-ai/talamus/talamus-memory-talamus"><img src="https://agentmods.dev/badge/mcp/ampres-ai/talamus/talamus-memory-talamus/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/ampres-ai/talamus/talamus-memory-talamus"><img src="https://agentmods.dev/badge/mcp/ampres-ai/talamus/talamus-memory-talamus.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
talamus 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 12d 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
{
"talamus": {
"command": "uvx",
"args": [
"--from",
"talamus[mcp]==1.1.3",
"talamus-mcp",
"--root",
"${CLAUDE_PROJECT_DIR}",
"--read-only"
]
}
}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.
- 12d ago First seen · 13 lines scan A b3af2cec68d2
talamus is an MCP server published in the GitHub repository ampres-ai/talamus (3 stars, last pushed yesterday), 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
superlocalmemory
MCP server "superlocalmemory" as configured in qualixar/superlocalmemory. Launched with ${CLAUDE_PLUGIN_ROOT}/scripts/slm-launch. Needs 1 environment variable to run.
loreweave
Durable agent memory over a markdown vault: bitemporal facts, timelines, hybrid graph search. Runs locally from the loreweave npm package.
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.
agentmemory
Standalone MCP server for agentmemory — thin shim that re-exposes @agentmemory/agentmemory's MCP entrypoint. Runs locally from the @agentmemory/mcp npm package. Needs 3 environment variables to run.
code-review-graph
MCP server "code-review-graph" as configured in varun29ankuS/shodh-memory. Runs code_review_graph with python.
plur
Open, local-first engram memory for AI agents: read, correct, delete; shared over MCP. Runs locally from the @plur-ai/mcp npm package.