io.br8n/mcp
NPM · @BR8N/MCP
Owned, portable working memory: a plain-files markdown brain any model can read and cite.
Available components
Last scanned (19 hours ago)
Scores higher than 92% of npm servers
Category Memory and Knowledge
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 Security98
- 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
- 31 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to Branded-Mayhem-Collective-LLC/br8n). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 52 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability76
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 116 tokens (~38/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
- Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage78
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 33% 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
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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
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.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 26 −4
- Stability: pass → 0.77 functional
- 14 Oct 26 +1
- Stability: 0.97 → pass security
- 12 Oct 26 +1
- Security disclosure: unverified → fail ▼ functional
- 11 Oct 26 −1
- Security disclosure: fail → unverified ▼ functional
- 7 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 97. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Oct 26 −3
- Stability: pass → 0.80 functional
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 16 Oct 2026 · Analysed npm/@br8n/mcp@0.1.2
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 | Branded-Mayhem-Collective-LLC/br8n |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/Branded-Mayhem-Collective-LLC/br8n/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 2582071998 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:acee689a27cf06af452d4ffd34f6688f552cd38b05b85a98e0bae081a106e90692a8f65dd5c0845041c8dd5c999895b352d1bbfd02010a8360f4912ce |
Background: How many MCP packages publish verified provenance →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
brain_list ~24
List every markdown file in the brain (relative path, size, last modified).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
brain_read ~43
Read one file from the brain by relative path (e.g. decisions/2026-03-change-orders.md).
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | relative path inside the brain |
No output schema declared.
No examples provided.
brain_search ~49
Literal, case-insensitive search across the brain. Returns file, line number and the matching line, so answers can cite the source.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | – |
No output schema declared.
No examples provided.
How do I install the io.br8n/mcp server?
io.br8n/mcp runs locally as an npm package, launched with npx -y @br8n/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @br8n/mcp
claude mcp add io-br8n-mcp -- npx -y @br8n/mcp
What is the io.br8n/mcp server?
io.br8n/mcp is listed in the public MCP registry as io.br8n/mcp. Owned, portable working memory: a plain-files markdown brain any model can read and cite. This page covers its npm package (@br8n/mcp).
Is the io.br8n/mcp server safe to use?
io.br8n/mcp scores 90 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 16 October 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 io.br8n/mcp server expose?
io.br8n/mcp exposes 3 tools: brain_list, brain_read, brain_search. Their descriptions and schemas cost roughly 116 tokens of context every time the server is loaded.
Is the io.br8n/mcp server still maintained?
io.br8n/mcp is still listed as active in the MCP registry. We last reached this channel on 16 October 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 io.br8n/mcp server under?
io.br8n/mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.