ZenBrain MCP — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow-up value is specific to ZenBrain local SQLite memory across episodic and semantic layers: Do routing rules and repeated core-memory updates remain predictable through the early pre-1.0 tool changes?

Reviewed Oct 5, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Persistent local agent memory with layered storage and recall.

What we know

Local stdio MCP over a SQLite-backed seven-layer memory system for storing, recalling and consolidating episodic, semantic, procedural and core memories.

Maintenance / activity evidence

@zensation/mcp 0.1.9 published 2026-10-01T21:40:35.234Z

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Local read/write access to configured memory DB. Writes: Store/update memories; Consolidate/decay memory.
Authentication not yet verified.
Sensitive access: Potentially sensitive personal/work agent memory

Local-only reduces network exposure but persistent unencrypted memory needs filesystem protection.

Security source · policy file (attribution not established) ↗

Full authority, access and evidence limits are available in Review context and Access & risk.

All limitations / Review context

Do routing rules and repeated core-memory updates remain predictable through the early pre-1.0 tool changes?

The bounded review of the publisher's documented ZenBrain local SQLite memory across episodic and semantic layers and release notices identified no disclosed material condition preventing an accurately scoped public tracking entry. The resource's operational permissions remain uncertainty; this assessment does not certify installation safety.

Local-only reduces network exposure but persistent unencrypted memory needs filesystem protection.
Local read/write access to configured memory DB.
Memory stays local by default and package makes no network calls of its own; DB is plaintext unless separately protected.
Reviewed write actions: Store/update memories; Consolidate/decay memory
Sensitive access: Potentially sensitive personal/work agent memory
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited.
Documented tool authority and any remote data handling must be checked before installation or use.
Tool inventory, client matrix and permissions completeness were not requirements for this Radar tracking review.
Default recall is lexical rather than synonym-aware embeddings.
SQLite similarity search is intended for personal-scale memory.
Consolidation is manual/tool-triggered.
Default SQLite file is not encrypted.
Tool surface is documented as pre-1.0 and subject to change.
Publisher lifecycle: active early release

Original activity observations

@zensation/mcp 0.1.9 published 2026-10-01T21:40:35.234Z

Technical identity

npm/@zensation/mcp

Exact implementation source: https://www.npmjs.com/package/@zensation/mcp ↗
Reviewed resource type: MCP Server
Repository identity: zensation-ai/zenbrain
Package identity: npm:@zensation/mcp

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 5, 2026 · Latest source observation Oct 8, 2026

Package registry ↗
@zensation/mcp
Recorded package identity, distribution or download evidence.
Includes references whose attribution is not established.
GitHub repository ↗
zensation-ai/zenbrain
Repository reference; implementation attribution is not established for every document.
Includes references whose attribution is not established.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Warning

Not runtime tested, no third-party installation, network authorization, paid calls, or mutation executed.
Do not claim production service is available based on README alone.
Publisher documents client config; verify installed binary from config before claiming connected
V1 only gave global installation; corrected to publisher stdio launcher, Node 22+ and writable memory DB location.
Official npm publisher package page README inspected for this exact npm identity; static research only. Some setup statements are conservatively summarized; no source code or live client execution checked. V2 review did not run any live client.
Avoid write, payment, token transfer, publishing, sending, booking and remote account changes as tests.
Replace credential, action and registration placeholders; follow the matching publisher/client prerequisites. No execution performed.
Use the matching host, actual registration name and original installation environment; this does not revoke credentials.

Install / connect
Publisher instructions
Publisher documents client config; verify installed binary from config before claiming connected | Publisher npm README revisited on 2026-10-14; exact identity retained.
Reviewed setup example · Publisher instructions
npm install -g @zensation/mcp
Reviewed setup example · Publisher instructions
npx -y @zensation/mcp
Configure / authenticate
MCP100 setup guide
Requires Node.js 22+. Add to MCP client mcpServers: command npx; args ["-y","@zensation/mcp"]; env ZENBRAIN_DB="~/.zenbrain/memory.db" (publisher example). Use writable absolute/home path; relative path may resolve to / and fail. Verify the correct host/transport from the publisher README; secure credentials in local client settings.
Check connection
Suggested check
Check that the registered MCP tools are discoverable in the client; run only publisher-described read-only status/health tools if provided. No runtime verification was performed.
Remove / uninstall / revoke
MCP100 setup guide
If your Claude Code MCP registration is named `zensation-mcp`, run the client removal command. For Claude Desktop/Cursor/Codex or another registered name, remove the matching entry in that host’s MCP settings. Hosted OAuth disconnect and stopping a self-hosted process are separate; npx has no permanent global package install.
Remove named client registration · Claude Code only · MCP100 composed guide
claude mcp remove zensation-mcp

Official Documentation & Sources

What it does

Local stdio MCP over a SQLite-backed seven-layer memory system for storing, recalling and consolidating episodic, semantic, procedural and core memories.

Capability: Files & Knowledge
Resource type: MCP Server
Best fit: Persistent local agent memory with layered storage and recall.

Representative uses

Store/retrieve memories
Run recall across memory layers
Consolidate/decay memory
Use ephemeral `:memory:` mode

Limitations

Default recall is lexical rather than synonym-aware embeddings.
SQLite similarity search is intended for personal-scale memory.
Consolidation is manual/tool-triggered.
Default SQLite file is not encrypted.
Tool surface is documented as pre-1.0 and subject to change.
Publisher lifecycle: active early release

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: Not documented in the reviewed sources
Permissions: Local read/write access to configured memory DB.
Data handling: Memory stays local by default and package makes no network calls of its own; DB is plaintext unless separately protected.
Cost: free
Risk and cautions: Local-only reduces network exposure but persistent unencrypted memory needs filesystem protection.

Access scope and cautions

Write actions: Store/update memories Consolidate/decay memory
Sensitive access: Potentially sensitive personal/work agent memory
Risk level: moderate

FAQ

Based on reviewed evidence as of 2026-10-08. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Store/retrieve memories; Run recall across memory layers; Consolidate/decay memory; Use ephemeral `:memory:` mode.

What setup and authentication are documented?

Recorded installation/entrypoint step: npx -y @zensation/mcp. Recorded transport: stdio. Recorded environment-variable notes: ZENBRAIN_DB (optional); ZENBRAIN_CONTEXTS (optional). No configuration values are supplied here. Prerequisites: Node.js >=22; writable local SQLite path. These are the documented setup details, not a claim that installation or client compatibility was independently tested. Authentication: No account or network auth.

Can it modify data or perform write operations?

Documented write actions include: Store/update memories; Consolidate/decay memory. Recorded permission boundary: Local read/write access to configured memory DB.

What data-handling boundary should I consider?

Memory stays local by default and package makes no network calls of its own; DB is plaintext unless separately protected. Recorded sensitive-access context: Potentially sensitive personal/work agent memory.

What limitations and risks should I check before use?

Local-only reduces network exposure but persistent unencrypted memory needs filesystem protection. Default recall is lexical rather than synonym-aware embeddings. SQLite similarity search is intended for personal-scale memory. Consolidation is manual/tool-triggered. Default SQLite file is not encrypted. Tool surface is documented as pre-1.0 and subject to change. Publisher lifecycle: active early release. Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited. Documented tool authority and any remote data handling must be checked before installation or use.

Is this an official MCP?

Zensation AI is listed as First-party MCP in MCP100’s current evidence.