Is Agentmemory safe and trustworthy?

tashan scores Agentmemory on public evidence — tashan score 75.0/100, it is currently active, note: a single primary maintainer (bus-factor risk), no known advisories against the current release. Audit scope: OSV advisories, install-time scripts, build provenance and declared permission surface. We do not review source code or execute the capability.

How do I install Agentmemory?

In Claude Code: run `claude mcp add agentmemory-mcp -- npx -y @agentmemory/mcp`. In Cursor / Claude Desktop, add it to mcp.json / claude_desktop_config.json.

‹ The Index

Agentmemory

npm

Standalone MCP server for agentmemory — thin shim that re-exposes @agentmemory/agentmemory's MCP entrypoint

Works with: Claude Code, Cursor, Claude Desktop, Codex CLI, Gemini CLI, Cline, Windsurf, VS Code (installable)
installable: each client documents how to load an MCP server of this type — that is the client's promise, not a claim verified against this capability

Category: AI & Agents — see all ranked ›

Install (Claude Code):

claude mcp add agentmemory-mcp -- npx -y @agentmemory/mcp

tashan score: 75.0
Adoption: 18k/wk
Upkeep: 73.0
Freshness: 98.0
Evidence coverage: 100% of the inputs this score can use
Health: active
License: Apache-2.0

Security audit

Every finding is shown in full — which advisory, the version that fixes it, and the exact command run at install time. Nothing in this audit is behind a licence.

No known advisoriesclearchecked against OSV for 0.9.28 — this package, not its dependency tree

4 vulnerable dependenciesinstalls@opentelemetry/[email protected], @opentelemetry/[email protected], [email protected] — GHSA-8988-4f7v-96qf, GHSA-45rx-2jwx-cxfr · found by resolving all 230 packages this installs and querying OSV at the version each resolves to, not by name

No access inferred from declared dependenciesnothing it depends on reaches files, shell or network. This reads declarations only — built-in APIs are invisible to it, so absence of a declaration is not absence of access

No build provenanceno attestation — the published artifact cannot be traced to its source

You searched for one. Check the rest of your stack:

npx tashan-cli doctor

Reads the config already on your machine and names what is dead, deprecated or running code at install time. No account, nothing uploaded.

tashan Pro$6/mo

Agentmemory scores 75 today. Pro keeps the series, so you can see whether that is a project getting better or one on its way down.

Every score since we started measuring, for any capability
The named replacement when something you run is dying — not just that it is
tashan doctor over the config you already have, on your machine

Start a 7-day trial › Everything measured on this page stays free.

Show your score

Measured this well? Put the live badge in your README — it updates as the score does.

[![tashan](https://tashan.sh/badge/pkg-agentmemory-mcp.svg)](https://tashan.sh/capability/pkg-agentmemory-mcp.html)

npm ↗ · source ↗ · pkg:@agentmemory/mcp

Everything on this page is public evidence and free. What it cannot know is whether you run this — check your whole config, free, in the browser. tashan Pro adds the series behind each row and names a replacement for anything dying.

Already running this? Check your whole config — free, in your browser, nothing installed. Or npx tashan-cli doctor locally, which sends nothing at all.

Measured 2026-08-21 · scorer s5 · how · something wrong here?