Gnosem MCP server
online · 100% uptimedev.gnosem/gnosem·v1.0.0Cross-vendor AI memory over MCP. One semantic store, readable and writeable from every MCP client.
0 stars
Reviews
Write oneNobody has reviewed Gnosem yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Gnosem tools (6, 2 write)
write = sends, deletes, buys or postsmemory_forgetFreeSoft-delete a memory by id. The row is retained for audit but excluded from search/list and removed from the vector index.
memory_listFreeList 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 SQL level.
memory_searchFreeSearch 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' to run just one. Content defaults to the LLM-optimized (compressed) form when available (raw:true to invert). Excludes forgotten + superseded. Optional filters narrow after retrieval: tags (AND), written_by, session_id, and/or since/until (ms epoch).
memory_supersedeFreeReplace 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_writewrite actionFreeSave 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 structured-facts form optimized for LLM reading — the raw text is preserved. Pass no_optimize:true to skip. Writes are deduped by default: (1) SHA-256 of trim(content) short-circuits byte-identical writes with { id, exact_duplicate:true } for free (no embed call); (2) failing that, semantic dedup returns { id, deduped:true, matched_score } when cosine ≥ 0.85. Pass force:true to bypass both, or use memory_supersede to explicitly correct a prior memory.
memory_write_bulkwrite actionFreeWrite 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 { id, created_at, optimized? } on success, { id, created_at, deduped, matched_score } on dedup, or { error } on failure. Free-tier limits apply to the sum: if adding N would exceed 200, the first (200 - existing) succeed and the rest return an error.
Public scan report
scanner v0.1.9 · 2026-09-24 · same rubric, same numbers if you re-run it
- –Code scanremote-only server, no package to scann/a
- Live reliabilityremote reachable in 346ms20/20
- Tool poisoning6 tool descriptions checked15/15
- Auth qualityopen endpoint exposes 2 write-action tools with no auth3/15
- Maintenancelast push 30 days ago15/15
- Maintainer identityregistry namespace matches repository owner; website matches verified namespace9/10
Findings (1)
- highWrite-action tools reachable without authentication
auth.open-write
How Gnosem compares
Against every graded E-commerce MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 83/100
- higher than 77% of 2,174 E-commerce servers
- Tools
- 6
- the typical E-commerce server has 6
- Tools that change things
- 33%
- typical: 0%. Fewer write tools means less an agent can break
- Uptime
- 100%
- of our recent checks; the typical remote E-commerce server answers 100%
- Response time
- 121 ms
- faster than 82% of 1,527 E-commerce servers
What its tools let an agent do: 4 read · 2 change
Install Gnosem in Claude Code, Cursor or VS Code
claude mcp add --transport http gnosem https://gnosem.dev/mcp
What the publisher says
From the Gnosem repository's README, as published. We do not edit it. Read it on GitHub
Cross-vendor AI memory over MCP. One memory store. Every model. Claude, ChatGPT, Gemini, Kimi, Cursor, Windsurf — anything that speaks MCP.
gnosem.dev · pricing · llms.txt
What it is
Gnosem is a hosted Model Context Protocol server that gives each user one persistent memory store — readable and writeable from every MCP-capable AI client. Vendor-agnostic by design: a fact saved from Claude is visible in ChatGPT, Cursor, Windsurf, Zed, Kimi, and any other MCP client (or plain HTTP tool call) using the same API key.
The problem it solves: every AI vendor has its own proprietary memory. OpenAI's ChatGPT memory doesn't work in Claude. Anthropic's projects don't cross into GPT. Multi-model users retell context in every session. Gnosem is the neutral layer between vendors.
Tools exposed
- memorywrite — save a fact, preference, decision, or note. content, tags?, writtenby? (provenance), sessionid?, nooptimize?
- memory_search — semantic search across your memories. query, k?, raw?
- memory_list — list recent memories in reverse-chronological order. limit?, cursor?, raw?
- memory_forget — soft-delete a memory by id
- memory_supersede — replace a stale memory with a corrected one
AI-optimized storage
Long memories (>400 chars) are automatically compressed on write to a structured-facts form (Workers AI, llama-3.1-8b-instruct-fast) with a strict prompt: TOPIC=..., PROJECT=..., DECISION=..., STACK=..., PROBLEM=.... The reading LLM ingests the compact form by default — fewer tokens, same meaning. The raw prose is preserved and returned as contentraw; pass raw:true to invert. Pass nooptimize:true on write to skip compression entirely.
Compression is guarded — if the model output isn't actually shorter, gnosem falls back to storing raw only. Fail-open: any AI error still saves the memory.
Quickstart
npx gnosem-installAuto-detects and configures every MCP-capable client on your machine (Claude Desktop, Claude Code, Cursor, Windsurf, Zed). Prompts for your API key and merges the gnosem entry alongside your existing servers. Restart the affected clients — the five memory tools appear immediately.
Get an API key at gnosem.dev, or via the API:
curl -sX POST https://gnosem.dev/signup \
-H "Content-Type: application/json" \
-d '{"email":"you@example.com"}'The key is displayed once. Save it.
Manual config (any MCP client)
{
"mcpServers": {
"gnosem": {
"url": "https://gnosem.dev/mcp",
"headers": { "Authorization": "Bearer gn_your_api_key" }
}
}
}Quickstart — any HTTP client
# Write
curl -sX POST https://gnosem.dev/mcp \
-H "Authorization: Bearer gn_your_key" -H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"memory_write","arguments":{"content":"I prefer Postgres for greenfield work.","written_by":"claude-code","tags":["preference"]}}}'
# Search
curl -sX POST https://gnosem.dev/mcp \
-H "Authorization: Bearer gn_your_key" -H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"memory_search","arguments":{"query":"database preference","k":5}}}'Pricing
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Gnosem: common questions
- Is Gnosem MCP server safe?
- Mostly: it is graded B (83/100). Read the Gnosem safety report
- How do I install Gnosem?
- It runs remotely at gnosem.dev. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does Gnosem need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Gnosem maintained?
- The last commit was 70 days ago (2026-08-26). The latest release is v1.0.0.
- Is Gnosem up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.
- What can I use instead of Gnosem?
- Servers from other publishers that do the same job: Mneme Memory MCP server, Vectros AI MCP server and Kagura Memory Cloud MCP server.
- How does Gnosem compare with other E-commerce MCP servers?
- safety score 83/100 (higher than 77% of 2,174 E-commerce servers); tools 6 (the typical E-commerce server has 6); tools that change things 33% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.
Alternatives to Gnosem
Same job from other publishers: the closest match first, then the best rated.
- Mneme MemoryCross-session memory for AI coding agents via six tools; local-first SQLite store.not reviewedEstablishedA
- Vectros AITyped record store + hybrid search over MCP: deterministic lookups + semantic memory, per-customer.not reviewedGrowingB
- Kagura Memory CloudPersistent memory for AI assistants: store, search, and connect knowledge across conversations.not reviewedGrowingA
- Delx MemoryLocal-first persistent memory MCP: shared SQLite key/value store, searchable, TTL-aware, secret-safenot reviewedGrowingA
- Loki ModeAutonomous spec-to-product coding-agent CLI with an MCP server exposing 39 tools over stdio.not reviewedEstablishedB