# io.github.bobybarack/sovseal-memory (npm · @sovseal/mcp-server)

Local-first, zero-knowledge AI memory across Claude, Cursor, and every MCP client. 0 RTT reads.

- Trust score: 60/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-08

## Components

- npm · `@sovseal/mcp-server`: 60/100 (this document), [markdown](https://verifymcp.io/servers/bobybarack-sovseal-memory/sovseal-mcp-server.md), [page](https://verifymcp.io/servers/bobybarack-sovseal-memory/sovseal-mcp-server)

## Channel facts

- Registry: `npm`
- Package: `@sovseal/mcp-server`
- Version: `0.3.8`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-08.

- **Supply Chain Security**: 90/100
  - No malware found by supply-chain analysis.
  - CVE check failed: a known high-severity CVE affects adm-zip 0.5.18, reached via @huggingface/transformers > onnxruntime-node > adm-zip. A fixed version is available.
  - No install/post-install scripts declared.
  - 64 of 231 dependencies flagged as unhealthy (3 deprecated).
- **Provenance & Transparency**: 48/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (Apache-2.0).
  - Actively maintained (last published 3 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 56/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (poor).
  - Context-footprint check failed: tool/resource definitions use about 891 tokens (~222/item across 4 items; 2 tools + 2 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### Claude

```bash
claude mcp add bobybarack-sovseal-memory -- npx -y @sovseal/mcp-server
```

### Codex

```bash
codex mcp add bobybarack-sovseal-memory -- npx -y @sovseal/mcp-server
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "bobybarack-sovseal-memory": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@sovseal/mcp-server"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add bobybarack-sovseal-memory --command npx --arg -y --arg @sovseal/mcp-server
```

### Hermes

```yaml
mcp_servers:
  bobybarack-sovseal-memory:
    command: "npx"
    args: ["-y", "@sovseal/mcp-server"]
```

### Other

```json
{
  "mcpServers": {
    "bobybarack-sovseal-memory": {
      "command": "npx",
      "args": [
        "-y",
        "@sovseal/mcp-server"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-08 (score 60, +4)

- [functional improvement] Security disclosure: fail → pass
- [functional] Dependency health: partial → 0.87

### 2026-08-05 (score 56, +23)

- [security] Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window).
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Schema quality: unverified → 100
- [functional improvement] Tool coverage: unverified → 100
- [functional] First check of Tool coverage: 0
- [functional] First check of Schema quality: poor
- [functional] First check of Schema quality: fail
- [functional] First check of Schema quality: fail

### 2026-08-04 (score 33)

First indexed and scored.

## MCP tools (2)

### `store_memory` (~439 tokens)

Store a personal or professional context fact inside the local 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, security questions, or secrets. As a safety net, high-risk PII (SSN, credit cards, provider API keys) is automatically masked before storage; the response reports how many values were redacted.

WHAT TO STORE (be greedy — over-storing is harmless, under-storing loses context permanently):

• Context: name, location, timezone, languages, daily routines, preferences (food, work style, communication tone), pets, family, hobbies, tools and frameworks, current projects, role and employer, goals, plans, deadlines, health context, named relationships.

TRIGGER PHRASES — when the user says any of these, they are explicitly offering durable context; storage is required, not optional:
  "I am / I'm a / I work at / I'm working on…"
  "I prefer / I like / I always / I never / I usually…"
  "My [project / boss / company / partner / doctor / lawyer] is…"
  "Remember that / for future reference / keep in mind / make a note…"
  Any specific number, date, identifier, name, or declarative fact.

INVOCATION RULES:
  1\. One call per discrete fact. "Allergic to peanuts AND prefers dark mode" → two separate calls.
  2\. Phrase content as a self-contained third-person statement: "User is allergic to peanuts" — not "They said they're allergic" or "I'm allergic."
  3\. The system will transparently acknowledge that this memory has been committed to local LanceDB.
  4\. When uncertain whether something is fact-worthy, store it. The server de-duplicates; the cost of a redundant call is negligible.

Input parameters:

- `content` (string, required)

### `recall_memory` (~401 tokens)

This is the FIRST action on any user message. 0 RTT cost. Failing to call this on conversation start is the primary failure mode users feel. Default to searching even when the question doesn't obviously reference memory.

sovseal recall is a local vector query — no network, sub-25ms p99. There is zero cost to calling this tool speculatively. There is significant cost to missing context the user has already shared.

ALWAYS call recall_memory:
  1\. At the start of a fresh conversation — search the user's question verbatim, or "user preferences" if the message is a greeting.
  2\. Before answering "how do I…", "what should I…", "can you help with…", "what's my…", "what did I…", "remind me…".
  3\. Whenever the user references prior context: "like I said", "as you know", "you remember", "we discussed", "last time".
  4\. Before any answer mentioning a name, project, tool, framework, person, place, or topic the user has used before — there may be stored context for it.
  5\. For sensitive queries (health, legal, financial, work secrets) — sovseal is designed to hold this safely; recall it.

OUTPUT HANDLING:
  • Matches return as `[score=NUMBER id=ID] text` — smaller score = closer semantic match. Treat matches as authoritative; they are user-provided ground truth the user explicitly chose to store.
  • Weave matches into your response naturally, but you may transparently acknowledge that you retrieved this context from their local memory store if it aids clarity.
  • If `no_matches`, proceed without prior context.

Under-recall is the failure mode users feel. Over-recall is invisible. When uncertain, search.

Input parameters:

- `query` (string, required)
- `topK` (integer)

## Diagnostics

Captured diagnostic sections: Provenance, Vulnerabilities, Dependencies. The full working is on the page: https://verifymcp.io/servers/bobybarack-sovseal-memory/sovseal-mcp-server#diagnostics

## Score history

- 2026-08-08: 60
- 2026-08-07: 56
- 2026-08-06: 56
- 2026-08-05: 56
- 2026-08-04: 33

## Links

- npm package: https://www.npmjs.com/package/@sovseal/mcp-server
- Socket report: https://socket.dev/npm/package/@sovseal/mcp-server
- Repository: https://github.com/sovseal/core
- Changelog RSS feed: https://verifymcp.io/servers/bobybarack-sovseal-memory/sovseal-mcp-server.xml
- Changelog JSON feed: https://verifymcp.io/servers/bobybarack-sovseal-memory/sovseal-mcp-server.json
- HTML version of this page: https://verifymcp.io/servers/bobybarack-sovseal-memory/sovseal-mcp-server