dev.gnosem/gnosem · v1.0.0 · agents-and-memory
Gnosem is healthy: it completed an MCP handshake in 1579 ms and exposes 6 tools. It scores 63/100.
Cross-vendor AI memory over MCP. One semantic store, readable and writeable from every MCP client.
Endpoint: https://gnosem.dev/mcp (streamable-http)
Repository · Website · JSON · Add to my inventory
| health | 19.7 / 25 |
| authEase | 15 / 15 |
| toolQuality | 15 / 15 |
| maintenance | 5 / 15 |
| adoption | 0 / 10 |
| usage | 0 / 10 |
| security | 8 / 10 |
Scoring v0.3, computed 2026-10-15T02:36:22.716Z.
| Checked (UTC) | Status | Latency | Error |
|---|---|---|---|
| 2026-10-14T23:15:48.866Z | Healthy | 1579 |
memory_write | Save a fact, preference, decision, or note to the user's cross-model memory. Any MCP client can read this back later. Include written_by (e.g. 'claude-code', 'gpt-5', 'kimi-k2') for provenance and session_id to group related writes. Long content (>400 chars) is automatically compressed on write to a |
memory_search | Search the user's memories. Default mode is 'hybrid': blends semantic (cosine over Vectorize) and keyword (BM25 over SQLite FTS5) hits via Reciprocal Rank Fusion (k=60). Semantic catches paraphrases; keyword catches exact-string hits (IDs, dates, code snippets). Pass mode:'semantic' or mode:'keyword |
memory_list | List the user's most recent memories in reverse chronological order. Use for browsing or catching up on what the user's other model sessions have written recently. Same content/content_raw shape as memory_search. Optional filters (tags, written_by, session_id, since, until) narrow the listing at the |
memory_forget | Soft-delete a memory by id. The row is retained for audit but excluded from search/list and removed from the vector index. |
memory_supersede | Replace a stale memory with a corrected one. The old row is marked superseded and excluded from future reads; the new row becomes the current version. Use for corrections; use memory_forget for pure deletions. |
memory_write_bulk | Write up to 50 memories in a single call. Each entry runs the same path as memory_write (semantic dedup by default; pass force:true per-entry to skip). Embeddings + optimizations run in parallel; D1 inserts are batched. Returns { results: [...] } with one entry per input in the same order — each is |