brain-mcp (Marcin-Stanczyk/brain-mcp) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 12 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Emerging
74/100
21 days ago

brain-mcp

A local MCP server that acts as long-term memory for AI coding assistants, storing lessons and patterns in a local SQLite database with optional hybrid vector search via Ollama.

→ Marcin-Stanczyk/brain-mcp· listed on glama

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

Marcin-Stanczyk

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

Glama

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
✅
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configBRAIN_CODE_DIR~/code Directory that brain_scan_projects scans for projects
configBRAIN_DBrepo>/data/knowledge.db Path to the SQLite database file
configBRAIN_MIN_SIMILARITYwhich is why defaults to 0.5.
configBRAIN_RECURRENCE_THRESHOLD
configCODE_DIR
configBRAIN_STATE_DIR
configBRAIN_HOOK_MIN_SECONDS180 Sessions shorter than this are never asked for a lesson
configBRAIN_PROMPT_MAX_LESSONS
configBRAIN_PROMPT_MAX_LESSON_CHARS
configBRAIN_PROMPT_MAX_CHARS
configBRAIN_MIN_COVERED
configBRAIN_COVERAGE_RATIO
configBRAIN_W_LEXICAL
configBRAIN_W_VECTOR
configBRAIN_LEX_DEPTH
configBRAIN_MAX_COVERAGE_FLOOR
configBRAIN_HOOK_MAX_LESSONS12 Lessons injected at session start
configBRAIN_HOOK_MAX_CHARS4000 Hard cap on the injected block, so the hook can never balloon your context
configBRAIN_HOOK_MAX_GLOBAL4 Cap on those cross-cutting entries
configBRAIN_CODE_ROOT
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

12/12 tools missing one or more hints — brain_learn (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); brain_recall (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); brain_scan_projects (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +9 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

No arbitrary install scripts

Has postinstall/preinstall script — runs arbitrary code on npm install

Remove postinstall/preinstall hooks unless they’re essential.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 3 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/marcin-stanczyk/brain-mcp)](https://m8ven.ai/mcp/marcin-stanczyk/brain-mcp)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 1afe5c31335fff7a3ae091922b3f0c590104b864
code hash: 3c87ee17ef00b6d330739ff45bbcb89af81a67b51675931f17d19321841dc46f
verified: 8/21/2026, 1:52:58 AM
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client