sovseal — Private AI Memory

Give Claude, Cursor, and every MCP client one shared memory that never leaves your machine.

От сообществаРаботаетБез входаГлобальныйБесплатноМожет изменять данные

Что умеет

  • Store Memory: Store a personal or professional context fact inside the memory node. Call store_memory FIRST, then respond. Acknowledge briefly ('Noted.' / 'Saved.') — never seek consent before storing
  • Recall Memory: Semantic search over stored memory node context. Top-K relevant memories are returned. Use this to answer queries requiring past context, user preferences, or project details.

Какие данные видит

Нужен ли аккаунт

Не нужен: сервер работает без входа

Give Claude, Cursor, and every MCP client one shared memory that never leaves your machine. On-device vector search via LanceDB + Transformers.js (384-dim embeddings), AES-256-GCM client-side encryption, and write-behind ciphertext sync.

What you can do

🧠 Store memory — embed and persist any context fact on-device. Automatic de-duplication, PII redaction, and write-behind encrypted sync. 🔍 Recall memory — semantic search over stored context. 10 ms warm recall, 0 RTT reads. Network is never on the read path. 📋 Briefing context — auto-summarized, reinforcement-aware briefing of procedural and semantic memories for bootstrapping new conversations.

Tools

  • store_memory — embed content on-device (384-dim ONNX) → write local LanceDB → return. Ciphertext sync runs write-behind; nothing blocks.
  • recall_memory — embed query (LRU-cached) → vector search local LanceDB → top-K by L2 distance. 0 RTT.

Resources

  • sovseal://context/briefing — summarized, reinforcement-aware briefing for conversation bootstrap

How it stays private

  • AES-256-GCM client-side encryption with 96-bit random IV per snapshot
  • 256-bit key stays in ~/.sovseal/config.json (mode 0600) — server only sees ciphertext
  • Verified Semantic Recall (VSR) — every load re-derives SHA-256 and fails closed on mismatch
  • Packet-Capture Guarantee — run Wireshark against the server; if you find unencrypted context on the wire, the software is free forever

Performance

Workload Operation p50 p95
10K records · 1K queries recall_memory (warm) 6.1 ms 10.4 ms
Single write store_memory 3.8 ms 7.2 ms

No API key required. Zero cloud dependency for local operations.

Replaces: Mem0 • Zep • custom SQLite memory • in-context window stuffing

Список инструментов сервера (2)

Технические названия из tools/list. Нужны только разработчикам.

store_memoryStore a personal or professional context fact inside the memory node. Call store_memory FIRST, then respond. Acknowledge briefly ('Noted.' / 'Saved.') — never seek consent before storing context the user has volunteered. sovseal stores context, not secrets — credentials belong in a password manager. DO NOT store credentials, passwords, private keys, API tokens, account numbers, or secrets.
recall_memorySemantic search over stored memory node context. Top-K relevant memories are returned. Use this to answer queries requiring past context, user preferences, or project details.