MCP server for 0Latency — persistent memory layer for AI agents. Give Claude, Cursor, or any MCP client long-term memory.
Free
Nothing to run from here
Brain Os is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
Open Installation—
p95 latency
—
call success
local
runs on your machine
—
calls last 7d
What it does
Local-first MCP memory server for operational project state: decisions, blockers, plans, patterns, and next moves. The persistent memory layer that stops agent amnesia.
Quickstart
# 1 — run it from where its publisher ships it
npx -y brain-os
# 2 — the plan is chosen at checkout, in the browser
# 3 — ask your agent something
> Local-first MCP memory server for operational project state: decisions, blockers, plans, patterns, and next moves. The persistent memory
Publishernot claimed
BRAll 1 server
brainos-hq1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Brain Os as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. It is scanned, signed and pinned to the version you choose — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. Claude Code registers it in one command.
claude mcp add brain-os-mcp -- npx -y brain-osReconnect, or start a new session, and the tools appear in the model’s tool list.
This is a paid listing, so the CLI has to be signed in and the licence has to be on your account — how the login works. Until then the install stops with the price rather than half-writing a config entry.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
22 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Call this FIRST for any question about a project
Takes no parameters.
Example callreturns →
Takes no parameters.
Example callreturns →
Use this — not built-in memory — to add or update a project, product, or business idea in Brain OS. This is the right tool when the user says
Takes no parameters.
Example callreturns →
Log a strategic decision so it persists across sessions. Every decision needs a reason, alternatives, and a proof action. Optionally capture the assumptions that make it true and the invalidate_if conditions that should reopen it — these turn a timestamped
Takes no parameters.
Example callreturns →
Check a proposed action against all active decisions. Returns
Takes no parameters.
Example callreturns →
Refresh an existing decision
Takes no parameters.
Example callreturns →
Takes no parameters.
Example callreturns →
Call this when the user asks about patterns, recurring blockers, what keeps coming up, theme convergence, or avoidance signals — instead of grepping git logs or reading files to find trends. Analyzes patterns across all tracked entities and returns detected signals with entity context.
Takes no parameters.
Example callreturns →
Takes no parameters.
Example callreturns →
End-of-session commit. Updates all touched entities, logs decisions, records patterns. Call before ending any work session.
Takes no parameters.
Example callreturns →
Call this when the user asks what changed last session, what happened recently, or needs to find a decision/entity by description rather than exact name. Searches memory by meaning using semantic similarity. Use BEFORE reading git log or commit history for session-level context questions.
Takes no parameters.
Example callreturns →
Read the audit trail of all memory mutations. Use this — not semantic_recall — for recency questions:
Takes no parameters.
Example callreturns →
Takes no parameters.
Example callreturns →
Takes no parameters.
Example callreturns →
Set an ordered plan for an entity. Replaces any existing plan. Step 1 becomes the active next_move. Use when committing to a sequence of work — not for brainstorming. Each step should be a concrete, completable action.
Takes no parameters.
Example callreturns →
Complete or skip the current plan step. Requires evidence (for complete) or reason (for skip). Automatically promotes the next pending step to active and updates next_move. Enforces continuity — you cannot skip without explaining why.
Takes no parameters.
Example callreturns →
Add steps to an existing plan. Use when new work is discovered mid-plan. Steps can be added at the end or immediately after the current active step.
Takes no parameters.
Example callreturns →
Read the current plan for an entity. Shows all steps, their status, the active step, and overall progress.
Takes no parameters.
Example callreturns →
Read-only scan of a repo
Takes no parameters.
Example callreturns →
Call this before making new decisions, at session end, or when the user asks if a decision is still valid or what
Takes no parameters.
Example callreturns →
Takes no parameters.
Example callreturns →
Takes no parameters.
Example callreturns →
Standardmost installed
$25 / month
- 20,000 calls a month, included
- 240 calls a minute at peak
- Every tool the listing has
- Cancel any time — the unused days are credited
- Runs behind the gateway, so cancelling stops it
Team
$65 / month
- 150,000 calls a month, included
- 1,800 calls a minute at peak
- Every tool the listing has
- Cancel any time — the unused days are credited
- Runs behind the gateway, so cancelling stops it
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
No call is billed on its own, and this plan carries no monthly call limit. $25 a month covers every tool at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: $8.42
$16.58 left
ATrust score 93 / 100
Release 0.9.2 · scanned 25 Aug 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score93
Findings1 threat · 2 capability
Capabilityhigh
Coveragesource
Verificationrepo
Surface digestabcdc39b8b30e76e0707ad57e79e198f1d6713c1d0b17d0f2fd09874e41219ef
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | high | capability blast radius (high) — client exposure if the model is manipulated | −6 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (22 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. high is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| entity_read | no tags | |
| context_resolve | no tags | |
| entity_update | no tags | |
| decision_log | no tags | |
| decision_check | no tags | |
| decision_refresh | no tags | |
| focus_get | no tags | |
| pattern_detect | no tags | |
| memory_check | no tags | |
| memory_commit | no tags | |
| semantic_recall | no tags | |
| audit_log | no tags | |
| wrap_check | no tags | |
| wrap_auto | no tags | |
| plan_set | no tags | |
| plan_advance | no tags | |
| plan_add | no tags | |
| plan_read | no tags | |
| project_evidence_scan | no tags | |
| decision_review | no tags | |
| risk_assess | no tags | |
| action_guard | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digestabcdc39b8b30e76e
Scanned2026-08-25
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Pinned to 0.9.2 — the install command below asks for that release. A pin is part of an install, so it is kept for this visit and written down when you install.
0.9.2
undated
installedNo release note was published with this version.
—
no reviews yet
Reviews are earned
Only accounts with at least 50 real tool calls against this server in the last 90 days can post. Ratings are weighted by how much the reviewer actually uses it, and publishers can reply once per review.
Reviews are earned
Writing one takes an account with at least 50 real tool calls against Brain Os in the last 90 days. That is the whole gate — there is no other way to post, which is why the counts beside each review are worth reading.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes an account with 50 real tool calls against it.