# Brownmatter Brainz MCP server

Source: https://glimind.com/server/mcp-registry%2Fai.brownmatter%2Fbrainz
Registry id: `mcp-registry/ai.brownmatter/brainz`
Status: live (checked 2026-11-22T17:15:43.128Z)

## Verdict

Brownmatter Brainz MCP server answered 99.98% of Glimind's liveness checks over 30 days, better than 38% of MCP servers, with 566 ms median handshake and 2 outages in 90 days. Its agent-readiness grade is A (92/100) across 18 tools, costing an agent about 6,935 tokens to load. Checked every few minutes; no tool is ever called.

## Measurements (30 days)

| Metric | Value | Better than |
|---|---|---|
| Uptime, 30 days | 99.98% | 38% of MCP servers |
| Median handshake latency | 566 ms | 19% of MCP servers |
| p95 handshake latency | 1077 ms | — |
| Checks in 30 days | 5,439 | — |
| Outages, 90 days | 2 | — |
| Median recovery | 2 min | — |
| Agent-readiness score | 92/100 (A) | 65% of MCP servers |
| Tools | 18 | — |
| Tool-list size for an agent | ~6,935 tokens | 25% of MCP servers |
| Days observed | 24 | — |

## Install

```json
{
  "mcpServers": {
    "brownmatter-brainz-mcp-server": {
      "type": "http",
      "url": "https://brainz.brownmatter.ai/mcp"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http brownmatter-brainz-mcp-server https://brainz.brownmatter.ai/mcp
```

## Tools (18)

- `burndown`: Burndown and flow metrics for the vault's tasks, computed from their recorded history. `scope` is a concept id (an iteration, milestone, feature, domain or any 
- `complete_task`: Mark a task done. Sets taskStatus=done + doneAt and appends `outcome` to the task body as an Outcome section. The result carries a one-line `reminder` that the 
- `create_task`: Turn a finding into first-class work: creates a `task`-type concept with taskStatus=open and the given relations — part_of a domain and/or an epic, `realizes` s
- `create_vault`: Create a new, empty vault owned by you and add it to this connection. Returns the new vault and the vaults this connection can now use. Once a connection covers
- `delete_concept`: Remove a concept from the vault and all of its outgoing edges. Use to clear a note that is wrong, obsolete, or junk (e.g. a probe or test node that shouldn't be
- `dream`: Dreaming: a scheduled consolidation sweep over this vault. Light stages what changed since the last dream (near-duplicate concepts, finished task outcomes, hygi
- `get_concept`: Fetch one concept by exact id: full markdown body, metadata, and its direct graph neighbors (each with the relation that connects it). Use after search_concepts
- `get_context`: Assemble a markdown briefing of the concepts most relevant to a query and/or explicit ids, expanded through the graph and trimmed to a token budget. The briefin
- `get_related`: Walk the knowledge graph outward from a concept and return everything within `depth` hops, with distance and the edge path that reached it. Use to map the blast
- `link_concepts`: Add a typed, directed edge between two existing concepts by editing the `from` note's frontmatter (e.g. lead-scoring depends_on contact-model). Use when you not
- `list_concepts`: Enumerate concept metadata (no bodies), optionally filtered by product, type, or a single tag. Use to get the lay of the land in an unfamiliar vault, to audit w
- `list_tasks`: List the vault's work pile: `task`-type concepts with their lifecycle (open/taken/done), oldest first, including who has taken each one (takenBy). Filter by tas
- `onboard`: Index an existing product's codebase into this vault. {action: "start"} returns the onboarding playbook: a method for surveying the codebase and recording its p
- `search_concepts`: Search the product knowledge vault by free-text query. Useful when you need product knowledge but don't yet know which concept ids exist. Returns ranked hits (i
- `sync`: Re-index an onboarded vault after the code changes (drift). {action: "start"} returns the sync playbook: the vault's last_synced_at, a coverage map over the con
- `take_task`: Claim a task and get its briefing in one call. Pass an `id` to claim a specific task, or omit it to claim the next open task (oldest open by createdAt then id).
- `upsert_concept`: Write a concept note into the vault (creates or overwrites the markdown file, then reindexes it). Use to capture new product knowledge discovered during a task 
- `vault_stats`: Summarize the vault: counts of concepts and edges, the products and tags in use, a breakdown by concept type, and whether semantic search is available. Useful f

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.
