amem vs com.uluplife/life
amem is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑17.
amem is a plugin bundle for AI coding tools published by Aman Asmuei. No marketplace we read lists it any more. com.uluplife/life is an MCP server published by uluplife.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-25. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |  com.uluplife/life | |
|---|---|---|
| Community marketplace amanasmuei/amem | Removed on 2026-10-17 Version: 0.15.0 Forks (GitHub): 1 Stars (GitHub): 2 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.0 No figure published Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | amemno longer listed · | com.uluplife/life |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 2 | No figure on GitHub |
| Forks (GitHub) (differs) | 1 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (@aman_asmuei/amem) | Remote server (www.uluplife.com/api/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Hooks it runs (differs) | 3 | Not published |
| Parts of the bundle (differs) | 9 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/amanasmuei/amem | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-14 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Not responding since 2026-10-24 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of amem
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
engram io.github.tstockham96/engram
Intelligent agent memory with automatic extraction, consolidation, and bi-temporal recall.
-
Graph-native persistent memory for AI agents — 33 MCP tools, zero-LLM writes.
-
Cross-session memory for AI coding agents via six tools; local-first SQLite store.
-
One shared, persistent memory across AI agents and systems, with semantic recall and live updates.
-
Persistent memory for Claude Code with hot cache instant recall and semantic search. Give your AI assistant a second brain.
-
A dual-path memory system for proactive agents: a typed knowledge graph with evidence, contradictions and supersession, maintained in the background on a small model. No API key…
What each says it does
amem
Persistent memory layer for AI — typed, scored, temporal, searchable. 28 tools, knowledge graph, privacy controls.
com.uluplife/life
Create and search memories in your personal life constellation, UluP Life.
How to run each
amem
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
com.uluplife/life As a remote MCP server
claude mcp add --transport http life https://www.uluplife.com/api/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only com.uluplife/life has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: amem · What it can do: com.uluplife/life · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.