Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

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.

Available components

0 this week 77 Trust /100

Last scanned (18 hours ago)

Scores higher than 56% of npm servers

Category Memory and Knowledge

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Supply Chain Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 67 of 229 dependencies flagged as unhealthy (3 deprecated). View diagnostics → Partial
Provenance & Transparency48
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (Apache-2.0).Pass
  • Actively maintained (last published 108 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability77
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Nov 26 0
    • Stability: 0.97 → pass security
  • 20 Nov 26 0
    • Stability: pass → 0.97 functional
  • 14 Nov 26 0
    • Stability: 0.97 → pass security
  • 13 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 9 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

  • 7 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

  • 4 Nov 26 −4
    • Stability: pass → 0.67 functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Analysed npm/@sovseal/mcp-server@0.3.8

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Vulnerabilities 12 findings
ID CVE Severity Vector Fix available
GHSA-7q85-xj36-vmfc CVE-2026-77301 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-8238-w5pm-2374 CVE-2026-114102 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-c6fg-446q-cg94 CVE-2026-114103 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L yes
GHSA-j5f4-cc29-5x44 CVE-2026-102282 high CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N yes
GHSA-p634-w6r4-rjp2 CVE-2026-114104 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N yes
GHSA-rcw4-f5rp-g42v CVE-2026-92000 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-vwc7-r8mq-g2x9 CVE-2026-76845 medium CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:N no
GHSA-xcpc-8h2w-3j85 CVE-2026-39244 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-f88m-g3jw-g9cj CVE-2026-114113 high yes
GHSA-rgj7-g3m4-5g8c CVE-2026-114112 high yes
GHSA-wq5f-xc86-pv6w CVE-2026-114111 high yes
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 229 packages
Packages resolved 229
Deprecated 3
Stale 65
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 2 exposed · ~840 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
recall_memory ~401

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.

NameTypeReqDescription
querystringyes–
topKinteger––

No output schema declared.

No examples provided.

store_memory ~439

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.

NameTypeReqDescription
contentstringyes–

No output schema declared.

No examples provided.

Install

How do I install the io.github.bobybarack/sovseal-memory MCP server?

io.github.bobybarack/sovseal-memory runs locally as an npm package, launched with npx -y @sovseal/mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @sovseal/mcp-server

# add to Claude Code
claude mcp add bobybarack-sovseal-memory -- npx -y @sovseal/mcp-server
Common questions

What is the io.github.bobybarack/sovseal-memory MCP server?

io.github.bobybarack/sovseal-memory is an MCP server listed in the public MCP registry as io.github.bobybarack/sovseal-memory. Local-first, zero-knowledge AI memory across Claude, Cursor, and every MCP client. 0 RTT reads. This page covers its npm package (@sovseal/mcp-server).

Is the io.github.bobybarack/sovseal-memory MCP server safe to use?

io.github.bobybarack/sovseal-memory scores 77 out of 100 on VerifyMCP. We recorded 12 known advisories against it as of 21 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.bobybarack/sovseal-memory MCP server expose?

io.github.bobybarack/sovseal-memory exposes 2 tools: store_memory, recall_memory. Their descriptions and schemas cost roughly 840 tokens of context every time the server is loaded.

Is the io.github.bobybarack/sovseal-memory MCP server still maintained?

io.github.bobybarack/sovseal-memory is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.bobybarack/sovseal-memory MCP server under?

io.github.bobybarack/sovseal-memory declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the io.github.bobybarack/sovseal-memory MCP server?

VerifyMCP ran 16 checks on io.github.bobybarack/sovseal-memory, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.