brainfile
Registry code: 3228b90fe96c0d96
Brainfile — the memory layer / operating system for Claude Code. Call list_pack_contents to see everything Brainfile ships, get_starter_file for the free on-ramp (INTERVIEW-ME.md / START-HERE.md / CLAUDE.starter.md), and get_freshness_sample for the weekly living-system update. Start a no-card 30-day trial at https://brainfile.io/trial?utm_source=mcp&utm_medium=mcp_tool&utm_campaign=initialize.
- endpoint
- https://brainfile.io/mcp
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is brainfile live?
- Yes — it answered the hub's last check (checked 9h ago). It answered 99% of checks over the last 30 days.
- Is brainfile free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does brainfile have?
- 3 tools: get_starter_file, get_freshness_sample, list_pack_contents.
- Is brainfile safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 99.3%· all time 99.3%
last good check
of 3 tools
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- topic
- ai & agents memory & context
- used for
- list the brainfile pack contents
- get free starter files for claude code
- get the weekly update sample
- takes → gives
- text → text
- tools
- 3 reads
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
get_starter_file reads open 40d ago
Get the REAL Brainfile free-tier starter files — the on-ramp that turns generic Claude into a project that remembers you. Full text, no account needed. Files: INTERVIEW-ME.md (first-session interview that personalizes your CLAUDE.md), START-HERE.md (orientation + first prompt), CLAUDE.starter.md (starter operating-system playbook). Omit 'name' to get all three.
{ "type": "object", "properties": { "name": { "enum": [ "INTERVIEW-ME.md", "START-HERE.md", "CLAUDE.starter.md" ], "type": "string", "description": "Which starter file to fetch. Omit for all three." } } }arguments 14 linesget_freshness_sample reads open 9h ago
Get the real Brainfile freshness feed entry that ships in the pack — the weekly 'living system' update (the same improvements we run on our own six live businesses + what changed in Claude Code, with how to apply each to your brain/). This is the retention mechanic; a paid license keeps the newest feed flowing.
{ "type": "object", "properties": {} }arguments 4 lineslist_pack_contents reads open 9h ago
List the full Brainfile pack manifest: the v1 pattern files (Autopilot protocol, never-empty backlog, never-forgets ledger, interview onboarding, end-of-run brief template, conversation-history pattern, freshness feed — each with a one-line description; starter files fetchable right here over MCP, the rest via the free no-card trial pull), plus the paid role packs (15) — listed but locked, with the unlock URL. Use this to see everything Brainfile ships before starting a trial.
{ "type": "object", "properties": {} }arguments 4 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id3228b90fe96c0d96.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/3228b90fe96c0d96/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/3228b90fe96c0d96?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.