Brain Os MCP Server
brain-os
npm
v0.9.2
Published by brainos-hq — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.
Local-first MCP memory server for operational project state: decisions, blockers, plans, patterns, and next moves. The persistent memory layer that stops agent amnesia.
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 7 = 93. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −6 | capability blast radius (high) — client exposure if the model is manipulated |
| −1 | publisher verification (public source) — no provenance, but the source is public and inspectable |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
Findings 3
high Shell/command execution in server code (dist/tools/project-evidence-scan.js)MTC-SRC-002
In the server's implementation (`dist/tools/project-evidence-scan.js:3`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: ecFileSync } from "node:child_process"; // Root-level files we know carry operating state. Matched case-insensitively //
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/tools/project-evidence-scan.js
medium Hardcoded egress to an external endpoint (dist/index.js)MTC-SRC-003
In the server's implementation (`dist/index.js:20`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: const res = await fetch("https://registry.npmjs.org/brain-os/latest"); if (!res.ok) return;
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/index.js
medium Dynamic module load from a non-literal (dist/utils/embeddings.js)MTC-SRC-005
In the server's implementation (`dist/utils/embeddings.js:43`): Loading a module chosen at runtime (from a variable) can pull in and run attacker-influenced code paths. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: providerModule = await import(OPENAI_PROVIDER_PACKAGE); const OpenAI = providerModule.default;
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/utils/embeddings.js
Tools 22
Each tool and what it can reach — statically extracted from the published source.
action_guardno sensitive capabilityaudit_logno sensitive capabilitycontext_resolveno sensitive capabilitydecision_checkno sensitive capabilitydecision_logno sensitive capabilitydecision_refreshno sensitive capabilitydecision_reviewno sensitive capabilityentity_readno sensitive capabilityentity_updateno sensitive capabilityfocus_getno sensitive capability
Show 12 more tools ↓
memory_checkno sensitive capabilitymemory_commitno sensitive capabilitypattern_detectno sensitive capabilityplan_addno sensitive capabilityplan_advanceno sensitive capabilityplan_readno sensitive capabilityplan_setno sensitive capabilityproject_evidence_scanno sensitive capabilityrisk_assessno sensitive capabilitysemantic_recallno sensitive capabilitywrap_autono sensitive capabilitywrap_checkno sensitive capability
What this scan could not see
- 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>".
Versions 2
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v0.9.2 latest |
A 93/100 | 3 | 1.13.0 | 2026-09-07 |
v0.9.1 |
A 93/100 | 2 | 1.12.1 | 2026-08-21 |
Embed this score
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
Verify this score yourself
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan brain-os --onlineMore in AI, Memory & Reasoning
FDA device & vehicle recall risk for AI agents: recall history, MAUDE trend, risk score.
Open-source MCP server exposing Agent402.Tools' catalog — 500+ strong: 400+ self-hostable tools + 100 multi-tool skill packs (security-audit, trend-analysis, structured-scrape, decode-blob, forecasting-bake-off) for AI agents — browser, web search & answe
Zero-dependency MCP server that gives AI agents a self-updating project memory in AGENTS.md. Returns merge instructions instead of mutating state, so every change is a reviewable diff.
MCP Apps UI resources and server helpers for n8n
MCP server providing comprehensive access to BookStack knowledge management system
MCP server for tracking achievements with STAR methodology