All servers · Documents & retrieval · Databases · Scraping & browsing
Gnosem
dev.gnosem/gnosem · v1.0.0
Measured by MCP Station
| Last check | Reachable |
|---|---|
| Checked at | — |
| Check success 7 / 30 days | — |
| First-try success 30 days | — |
| Median response | — |
| Lookups 30 days | — |
| Authentication | No auth |
| MCP version | 2025-06-18 |
| Rank score | — |
| Declared risk | Not declared (tools carry no read/destructive hints) |
| Capabilities declared | tools |
| Tool definitions | 6 tools · with description 100% · input schema is an object 100% · read/destructive hints 0% |
Description written by the publisher, not verified
Cross-vendor AI memory over MCP. One semantic store, readable and writeable from every MCP client.
Connect
streamable-http · https://gnosem.dev/mcp
claude mcp add --transport http gnosem https://gnosem.dev/mcp{
"mcpServers": {
"gnosem": {
"url": "https://gnosem.dev/mcp"
}
}
}Tools as reported by the server
memory_writeSave 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 amemory_searchSearch 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:'keywordmemory_listList 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 thememory_forgetSoft-delete a memory by id. The row is retained for audit but excluded from search/list and removed from the vector index.memory_supersedeReplace 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_bulkWrite 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
Repository · Website · JSON · Text for agents · Registry updated 2026-07-30