MCP Uptime
← MCP Reliability Index  /  AI & LLM
G

Gnosem

dev.gnosem/gnosem
Cross-vendor AI memory over MCP. One semantic store, readable and writeable from every MCP client.
healthy
status
6
tools exposed
2450ms
connect latency
0cfb61279fa0
schema fingerprint

Tools (6)

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

Endpoint

https://gnosem.dev/mcp
Category: AI & LLM · Last checked: 2026-08-15T09:21:41Z

Monitor your own MCP server

Get alerted the moment yours goes down, a tool schema drifts, or an upstream silently breaks.

Get early access
How we measure →
What this means. This server responded to the MCP handshake and listed its tools without authentication. The schema fingerprint lets us flag if tool signatures silently change (schema drift) between checks.