amem
NPM · @IAMEM/AMEM
Local, private memory for coding agents: facts, skills and tasks that persist across sessions.
Available components
Last scanned (1 hour ago)
Scores higher than 34% of npm servers
Category Memory and Knowledge
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security90
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Declares code that runs automatically (postinstall) and that we could not recognise. It may be perfectly ordinary, but we have not established what it does. View diagnostics → Partial
- 24 of 38 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 4 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability72
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1734 tokens (~108/item across 16 items; 16 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
- Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage87
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 62% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 16 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +26
- Malware scan: unverified → pass ▲ security
- Known CVEs: unverified → pass ▲ security
- Dependency health: unverified → 0.68 ▲ functional
- 31 Oct 26 −10
- Known CVEs: pass → unverified ▼ security
- Malware scan: unverified → pass ▲ security
- Dependency health: 0.68 → unverified ▼ functional
- Schema quality: pass → fail ▼ functional
- Package version: 0.7.3 → 0.7.5 functional
- Package version: 0.7.3 → 0.7.4 functional
- 30 Oct 26 −12
- Known CVEs: pass → unverified ▼ security
- Malware scan: pass → unverified ▼ security
- Schema quality: 92 → 106 ▼ functional
- Dependency health: 0.68 → unverified ▼ functional
- Tool coverage: 45% → 62% ▲ functional
- Stability: unverified → 0.13 ▲ functional
- Package version: 0.4.3 → 0.7.3 functional
- Package version: 0.4.3 → 0.6.0 functional
- Package version: 0.4.3 → 0.5.0 functional
- Package version: 0.4.3 → 0.4.4 functional
- 27 Oct 26 +25
- Malware scan: unverified → pass ▲ security
- Known CVEs: unverified → pass ▲ security
- Dependency health: unverified → 0.68 ▲ functional
- 26 Oct 26 37
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/@iamem/amem@0.7.5
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| postinstall | unreviewed | node ./scripts/postinstall.js |
Background: Why install scripts are a supply-chain risk →
Dependencies 38 packages
| Packages resolved | 38 |
|---|---|
| Deprecated | 1 |
| Stale | 23 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
amem_context ~82
Retrieve compact local amem memory for a query. Use before exploring files or calling a remote LLM with a large prompt. Pass workspace for named app memory, not only git repos.
| Name | Type | Req | Description |
|---|---|---|---|
| platform | string | – | – |
| query | string | yes | – |
| sessionId | string | – | – |
| workspace | string | – | Named workspace (not a git repo) |
No output schema declared.
No examples provided.
amem_graph ~79
Dump stored facts for a workspace or git repo: claims, components, flows, and recent activity. Use when asked what amem remembers about a project. Prefer amem_context for a ranked packet for the current question. All arguments are optional.
| Name | Type | Req | Description |
|---|---|---|---|
| days | number | – | Activity lookback (default 30) |
| workspace | string | – | – |
No output schema declared.
No examples provided.
amem_recipe ~52
Return the generic amem remember contract: when to call amem_context vs amem_remember. Use if you are unsure whether to read or write memory. Same recipe for every MCP host. Takes no arguments.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
amem_remember ~159
Store a durable local fact in amem (stays on this machine). Use kind `private` (or anchor `private`) for personal, non-work facts so they never appear in work repositories' context. When the fact replaces an older one (a newer status, a fixed bug, a changed decision), pass the old claim ids in `supersedes` so the outdated memory stops being served. The response lists `possiblySupersedes`: older look-alikes to retire with amem_supersede if they are now wrong.
| Name | Type | Req | Description |
|---|---|---|---|
| anchors | array | – | – |
| kind | string | – | – |
| supersedes | array | – | Claim ids this fact replaces |
| text | string | yes | – |
| workspace | string | – | – |
No output schema declared.
No examples provided.
amem_repos ~79
List what amem is monitoring. Each item has kind git or workspace. Workspaces also have a stable slug (MCP id); the display name can differ. Use when asked which projects, workspaces, or repos amem knows about. All arguments are optional.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | all (default), git, or workspace |
No output schema declared.
No examples provided.
amem_skill_list ~82
List stored skills (procedures the agent learned) as an index of names and descriptions only. Cheap — call this first, then amem_skill_view to load the one you need. Skills are longer procedures; use amem_context for small durable facts. All arguments are optional.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | – | Optional: rank the index against this task description |
No output schema declared.
No examples provided.
amem_skill_save ~142
Save a non-trivial multi-step procedure you just worked out as a reusable skill. Use after solving something worth repeating — a workflow, a dead end you found the way past, or a correction the user gave you. Provide a full SKILL.md in `content`, or a description plus body.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | – | Full SKILL.md, or the markdown body to wrap |
| description | string | – | One line on when to use this skill |
| name | string | yes | Short slug, e.g. deploy-staging |
| sessionId | string | – | Optional conversation id, so amem can clear the nudge that prompted this |
No output schema declared.
No examples provided.
amem_skill_view ~110
Load the full body of one skill by name, or a supporting file inside it. Call this only after amem_skill_list (or the 'Relevant skills' section of an amem context packet) shows a skill worth following.
| Name | Type | Req | Description |
|---|---|---|---|
| file | string | – | Optional supporting file, e.g. references/api.md |
| name | string | yes | Skill name from amem_skill_list |
| sessionId | string | – | Optional conversation id, so amem can tell whether this procedure actually worked out |
No output schema declared.
No examples provided.
amem_stats ~102
Usage and savings stats (local lookup time, estimated tokens/ms saved, hit rate) for one workspace/repo or everything. Use when asked how much amem helped, how often it hit, or usage over time. All arguments are optional.
| Name | Type | Req | Description |
|---|---|---|---|
| days | number | – | Lookback window (default 30) |
| scope | string | – | all (every tracked repo/workspace) or current (the given workspace / cwd) |
| workspace | string | – | – |
No output schema declared.
No examples provided.
amem_status ~48
Binding, policy, and counts for one workspace/repo, plus the full monitored inventory. Omit workspace for a machine-wide overview. All arguments are optional.
| Name | Type | Req | Description |
|---|---|---|---|
| workspace | string | – | – |
No output schema declared.
No examples provided.
amem_supersede ~79
Retire outdated claims so they stop appearing in context: marks them superseded (kept for history, not served). Pass `by` with the claim id that replaces them, if any.
| Name | Type | Req | Description |
|---|---|---|---|
| by | string | – | Claim id of the newer fact (optional) |
| ids | array | yes | – |
| workspace | string | – | – |
No output schema declared.
No examples provided.
amem_task_add ~92
Create a deferred agent task on the project Kanban (default backlog). Use for work that should not get lost in chat. Durable facts still go through amem_remember.
| Name | Type | Req | Description |
|---|---|---|---|
| anchors | array | – | – |
| body | string | – | Why / notes |
| status | string | – | backlog | next | doing | blocked | done |
| title | string | yes | – |
| workspace | string | – | – |
No output schema declared.
No examples provided.
amem_task_complete ~128
Mark a Kanban task done as soon as its work is finished and verified, so the next session does not pick it up again. Records the completion time and keeps the task in history (amem_task_list with include_done shows it). Same as amem_task_update with status done. Returns the completed task as JSON; an unknown id returns an error.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Task id from amem_task_list or amem_task_add (task_…). |
| workspace | string | – | Workspace or repo name. Omit to use the repository the agent is running in. |
No output schema declared.
No examples provided.
amem_task_list ~84
List deferred agent tasks (Kanban) for a workspace/repo. Use for work to do later — not durable facts (use amem_remember for those). Default excludes done tasks. All arguments are optional.
| Name | Type | Req | Description |
|---|---|---|---|
| include_done | boolean | – | – |
| status | string | – | backlog | next | doing | blocked | done |
| workspace | string | – | – |
No output schema declared.
No examples provided.
amem_task_update ~203
Change an existing Kanban task: move it between columns (set status to doing when you start it, blocked when it waits on someone), rename it, or replace its notes or file anchors. Only the fields you pass change. Use amem_task_complete to finish a task and amem_task_add for new work. Returns the updated task as JSON; an unknown id returns an error.
| Name | Type | Req | Description |
|---|---|---|---|
| anchors | array | – | Repo-relative files the task touches; replaces the old list. |
| body | string | – | New notes; replaces the old notes entirely. |
| id | string | yes | Task id from amem_task_list or amem_task_add (task_…). |
| status | string | – | Kanban column. doing = being worked on now; blocked = waiting on someone or something. |
| title | string | – | New one-line title. |
| workspace | string | – | Workspace or repo name. Omit to use the repository the agent is running in. |
No output schema declared.
No examples provided.
amem_usage_report ~213
Report what you actually did with the last amem context packet, so its savings estimate becomes a measurement instead of a guess. Call this once after you have finished acting on a packet. Do NOT estimate tokens — just list which of the anchors amem gave you you ended up opening anyway (anchors_opened), and whether the packet answered the question without further exploration (answered). amem computes the saving from the real size of the files you did not have to open. Reporting that you opened everything is a useful and expected answer.
| Name | Type | Req | Description |
|---|---|---|---|
| anchors_opened | array | yes | File paths from the packet's Anchors lines that you actually read. Empty array if the claims alone were enough. Paths not in the packet are ignored. |
| answered | boolean | yes | True if the packet answered the question without broad exploration. False if you had to grep or read widely anyway. |
| event_id | string | – | Specific usage event. Omit to attest the most recent packet for this repo. |
| workspace | string | – | – |
No output schema declared.
No examples provided.
How do I install the amem MCP server?
amem runs locally as an npm package, launched with npx -y @iamem/amem. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @iamem/amem
claude mcp add sslugic-amem -- npx -y @iamem/amem
What is the amem MCP server?
amem is an MCP server listed in the public MCP registry as io.github.sslugic/amem. Local, private memory for coding agents: facts, skills and tasks that persist across sessions. This page covers its npm package (@iamem/amem).
Is the amem MCP server safe to use?
amem scores 67 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the amem MCP server expose?
amem exposes 16 tools: amem_context, amem_recipe, amem_remember, amem_supersede, amem_repos, and 11 more. Their descriptions and schemas cost roughly 1,734 tokens of context every time the server is loaded.
Is the amem MCP server still maintained?
amem is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the amem MCP server under?
amem declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.