@zensation/mcp

MCPattested
v0.1.6Zensation AIApache-2.0Updated 8d agonpmGitHub

MCP memory server for ZenBrain: agent memory for any Model Context Protocol client — store, recall, consolidate, health. Local SQLite file, no account.

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Attested build
A verified provenance attestation binds this artifact to the listed repository. Nobody has claimed the listing yet — this proves where the code was built, not who stands behind it.
247Downloads/wk
24GitHub stars
5Forks
8d agoLast update
Package
AuthorZensation AI
LicenseApache-2.0
Version0.1.6
Sourcenpm+mcp-registry
Trust Status
A
85/100Trusted
✓Listed in Forge index+10/10
✓Identity verified · attested build+20/20
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
✓npm Trusted Publishing (Sigstore)+5/5
—npm maintainer match+0/5
→ Publisher: add the verified GitHub login to the npm package's maintainers (npm owner add <login>)
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusIdentity verified
PublisherUnverified
SignatureUnsigned
Domain—
Provenance✓ Sigstore-verified · 2f65c70
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface4 tools · none privileged
Security scan✓ Cleanv0.1.3 · 1mo agoHow well does this scan work?
EvalsNone
IndexedAug 29, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

4 tools · none privileged
Statically extracted from the published packagev0.1.3 · 1mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

zenbrain_storeWrite something into long-term memory so it survives this conversation.

Write something into long-term memory so it survives this conversation.

No input schema was published for this tool.

zenbrain_recallSearch long-term memory for anything relevant to a query. Searches every layer

Search long-term memory for anything relevant to a query. Searches every layer

No input schema was published for this tool.

zenbrain_consolidateRun one consolidation pass: promote repeated episodes into semantic facts, decay

Run one consolidation pass: promote repeated episodes into semantic facts, decay

No input schema was published for this tool.

zenbrain_healthReport how full each of the seven layers is: working-memory slots in use,

Report how full each of the seven layers is: working-memory slots in use,

No input schema was published for this tool.

4 of 4 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

MCP memory server for ZenBrain: agent memory for any Model Context Protocol client — store, recall, consolidate, health. Local SQLite file, no account.

Keywords
mcpmcp-servermodel-context-protocolzenbrainagent-memoryai-memorymemory-layerlong-term-memoryepisodic-memorystateful-agentsllm-memory
Alternatives
Comparing tool surfaces…

Dependency tree

What one Forge scan resolved from npm metadata on 2026-08-30 — observed resolution, not a publisher declaration.

60 packages resolved · 4 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

58 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

+46 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.

Topics

Related in memory & knowledge graphs