Privacy
What leaves your machine.
The tool and this website are two different things with two different answers, and lumping them together would be the easy dishonest move. They are separated below.
The tool: telemetry is gone
brain-mcp used to ship anonymous usage telemetry. It was removed entirely in 0.4.1 and the endpoint it posted to was retired. The 2.0 rewrite (first released as 2.0.0-beta.1; the current release is 2.0.0) also dropped the only two modules that ever reached the network — the package no longer ships an HTTP client of its own.
The module still exists so that old imports do not crash, but every function in it now returns None and does nothing. You can read the whole thing in under a minute:
$ cat $(python3 -c "import brain_mcp,os;\
print(os.path.dirname(brain_mcp.__file__))")/telemetry.py
"""brain-mcp telemetry — REMOVED in 0.4.1.
Telemetry was removed entirely (and the endpoint it posted
to was retired). This module remains as a no-op shim so
existing imports keep working.
brain-mcp makes zero network calls at runtime.
"""
def is_enabled() -> bool: return False
def track(event, props=None): return None
def track_tool(...): return None
def flush() -> None: return NoneThat docstring is not quite true, and here is the exception. The first time brain-mcp builds its search index, DuckDB downloads its full-text-search extension (fts) from DuckDB's own extension repository and caches it under ~/.duckdb. It is a file download — nothing about you or your transcripts is sent — and it does not happen again once the extension is cached.
Apart from that one download, hooks, watchers, the spool, the floor, the manifest, the DuckDB cache and every recall tool run entirely on your machine, against files in your home directory. There is no account, no sync, no server component, and nothing to sign up for.
Prove it with one grep
Do not take that on trust — it is a claim about a codebase, and codebases change. A package that cannot make an HTTP request is a checkable property, so check it. Grep the installed package for every HTTP client Python has:
grep -rn "import httpx\|import requests\|import urllib.request\|\
import socket\|import openai\|import anthropic" \
$(python3 -c "import brain_mcp,os;\
print(os.path.dirname(brain_mcp.__file__))")In 2.0.0 it returns exactly one line: recorder/machine.py imports socket to call socket.gethostname(), which reads your machine's name locally to label your floor. It opens no connection. Earlier releases did have two opt-in paths that reached the network — a summarizer that called whichever LLM provider you configured, and a dashboard route that validated a pasted OpenRouter key. Both modules were removed in the 2.0 recorder rewrite; the package is now just the ingest and recorder trees.
If that grep ever returns anything else, this page is out of date and you should trust the grep, not the page. That is the intended relationship between the two.
Removing something you recorded
An append-only floor raises an obvious question: what if a transcript captured a credential, or something you simply do not want kept? brain-mcp redact replaces a span with a tombstone and records the redaction in the manifest. The content goes; the fact that a redaction happened stays, because a record that can be silently edited is not a record.
This website measures nothing about you.
No analytics script, no event log, no cookie, no localStorage id. Vercel, the host, sees the ordinary requests any web host sees, and that is all.
It used to say otherwise
Until 4 October 2026 this page said the site ran Vercel Analytics, Speed Insights and a first-party event log (page views, time on page, which install command was copied, with a random id kept in localStorage under _bmcp_sid). The database that log wrote to was shut down on 7 September 2026, and Vercel's analytics were never switched on for this project — so the page was describing measurement that was not happening, while every visit still sent a request to a dead endpoint. All three were removed from the site's code the same day this section was rewritten. If measurement ever comes back, this section changes in the same commit.
None of this touches the tool. Installing brain-mcp does not connect it to this site, and the site never receives anything about what you record or search.
In short
| Your transcripts | Never leave your machine. |
| The package (2.0.0) | Ships no HTTP client of its own. One file download on first run (DuckDB's search extension). No account, no sync. |
| Telemetry | Removed in 0.4.1. The shim that remains is a no-op you can read. |
| Redaction | brain-mcp redact tombstones a span and records the redaction in the manifest. |
| This website | No analytics, no cookie, no localStorage id. The host sees ordinary web requests. |
| Licence | MIT. |