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.

Make0 Brain

NPM · @MAKE0-AI/BRAIN

One shared, versioned memory for Claude Code, Cursor, Codex and every MCP agent. Local and offline.

Available components

+29 this week 81 Trust /100

Last scanned (23 hours ago)

Scores higher than 69% 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 Security99
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 44 of 167 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to make0-official/brain-oss). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 2 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability62
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1151 tokens (~164/item across 7 items; 7 tools + 0 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 Management23
  • Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage83
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 50% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 8 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
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.

  • 4 Nov 26 +1

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

  • 2 Nov 26 +11
    • Known CVEs: unverified → pass ▲ security
    • Dependency health: unverified → 0.89 ▲ functional
  • 1 Nov 26 +5
    • Known CVEs: pass → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Stability: 0.10 → unverified ▼ security
    • Malware scan: unverified → pass ▲ security
    • Dependency health: 0.89 → unverified ▼ functional
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
    • Package version: 0.2.4 → 0.3.1 functional
    • Package version: 0.2.4 → 0.3.0 functional
  • 31 Oct 26 +12
    • Provenance: fail → pass ▲ security
    • The attested source repository moved: make0-official/brain-oss security
    • Security disclosure: fail → pass ▲ functional
    • Package version: 0.2.3 → 0.2.4 functional
  • 30 Oct 26 −15
    • Malware scan: pass → unverified ▼ security
    • Package version: 0.2.2 → 0.2.3 functional
  • 29 Oct 26 +15
    • Known CVEs: pass → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Malware scan: unverified → pass ▲ security
    • Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
    • Dependency health: 0.89 → unverified ▼ functional
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • Stability: unverified → 0.03 ▲ functional
    • First check of Schema quality: unverified functional
    • Package version: 0.1.2 → 0.2.2 functional
    • Package version: 0.1.2 → 0.2.1 functional
    • Package version: 0.1.2 → 0.2.0 functional
  • 28 Oct 26 52

    First indexed and scored.

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 4 Nov 2026 · Analysed npm/@make0-ai/brain@0.3.1

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo make0-official/brain-oss
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/make0-official/brain-oss/.github/workflows/release.yml@refs/tags/v0.3.1
Rekor log index 3629732255
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:ce0c586ba1accb9e75c53d7aaf4485428bb33c8e1a126303d32e2b2d86f08b2a239129e923db99bd312281de88f50253a74d0670345d51f1d44738c6d

Background: How many MCP packages publish verified provenance →

Dependencies 167 packages
Packages resolved 167
Stale 44
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 7 exposed · ~955 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
add_memory ~205

Save a new Brain memory when the user explicitly asks to remember, save, or store something. Store either one singular fact or one short Markdown mini-doc (headings, lists, bold, links, code, and Mermaid diagrams) up to about 800 words. Use one memory for one coherent fact or note; do not paste a long document. A new memory that contradicts or restates an older one replaces it; the older one stays in version history.

NameTypeReqDescription
brainstringyesBrain id from list_brains. The personal brain is "personal".
categorystring––
confidencenumber––
contentstringyesMemory text: one singular fact, or one short Markdown mini-doc (headings, lists, bold, links, code, and Mermaid diagrams in ```mermaid fences). Keep it under about 800 words. Hard cap 4000 characters.
entityTypestring––
kindstring––

No output schema declared.

No examples provided.

delete_memory ~85

Delete a Brain memory when the user explicitly asks to remove a saved fact. The memory leaves search and reads, and every saved version is kept so the user can restore it with `npx @make0-ai/brain restore <id>`.

NameTypeReqDescription
brainstringyesBrain id from list_brains. The personal brain is "personal".
memoryIdstringyes–

No output schema declared.

No examples provided.

get_memory ~100

Fetch one Brain memory by id. Content is either a singular fact or a short Markdown mini-doc (up to about 800 words). The memory includes addedBy (who first saved it) and versionCount (saved revisions). When versionCount is greater than 1, call get_memory_versions to read every saved revision.

NameTypeReqDescription
brainstringyesBrain id from list_brains. The personal brain is "personal".
memoryIdstringyes–

No output schema declared.

No examples provided.

get_memory_versions ~87

Fetch every saved version of one Brain memory, newest first, including the current version. Use this when you need to see how a fact changed. Each version includes its full content. The version with current: true matches the memory returned by get_memory.

NameTypeReqDescription
brainstringyesBrain id from list_brains. The personal brain is "personal".
memoryIdstringyes–

No output schema declared.

No examples provided.

list_brains ~36

List Make0 brains this connection can use. Call this first to get a brain id for search_brain. Does not list memories.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

search_brain ~256

Search saved Brain memories. A memory may be a singular fact or a short Markdown mini-doc. Use a short, focused query with the key people, entities, preferences, or topics needed—not the full user message. Memories are retrieved with semantic + BM25 keyword search, reranked by a MiniLM cross-encoder, then expanded up to two hops along related_to graph links so connected memories surface with the seeds. Each memory includes addedBy (who first saved it) and versionCount (saved revisions). When versionCount is greater than 1, call get_memory_versions for the full history. Call get_memory whenever a result has truncated: true so you read the full note, not a clipped preview. Always pass brain from list_brains.

NameTypeReqDescription
brainstringyesBrain id from list_brains. The personal brain is "personal".
entityTypestring–Optionally restrict results to one memory entity type.
kindstring–Optionally restrict results to work or profile memories.
limitinteger–Maximum memories to return (1-64). Score-gated, then padded to at least 10 when candidates exist.
querystringyesFocused query for the saved facts needed.

No output schema declared.

No examples provided.

update_memory ~186

Update an existing Brain memory when the user asks to correct or change it. The new content can be a singular fact or a short Markdown mini-doc (headings, lists, bold, links, code, and Mermaid diagrams) up to about 800 words. New content replaces the old content, and the previous version is kept.

NameTypeReqDescription
brainstringyesBrain id from list_brains. The personal brain is "personal".
categorystring––
confidencenumber––
contentstring–Memory text: one singular fact, or one short Markdown mini-doc (headings, lists, bold, links, code, and Mermaid diagrams in ```mermaid fences). Keep it under about 800 words. Hard cap 4000 characters.
entityTypestring––
kindstring––
memoryIdstringyes–

No output schema declared.

No examples provided.

Install

How do I install the Make0 Brain MCP server?

Make0 Brain runs locally as an npm package, launched with npx -y @make0-ai/brain. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @make0-ai/brain

# add to Claude Code
claude mcp add make0-official-brain-oss -- npx -y @make0-ai/brain
Common questions

What is the Make0 Brain MCP server?

Make0 Brain is an MCP server listed in the public MCP registry as io.github.make0-official/brain-oss. One shared, versioned memory for Claude Code, Cursor, Codex and every MCP agent. Local and offline. This page covers its npm package (@make0-ai/brain).

Is the Make0 Brain MCP server safe to use?

Make0 Brain scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Make0 Brain MCP server expose?

Make0 Brain exposes 7 tools: list_brains, search_brain, get_memory, get_memory_versions, add_memory, and 2 more. Their descriptions and schemas cost roughly 955 tokens of context every time the server is loaded.

Is the Make0 Brain MCP server still maintained?

Make0 Brain is still listed as active in the MCP registry. We last reached this channel on 4 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 Make0 Brain MCP server under?

Make0 Brain declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.