{"name":"ai.brownmatter/brainz","title":"Brainz","url":"https://brainz.brownmatter.ai/mcp","host":"brainz.brownmatter.ai","read_at":"2026-11-10T15:26:19.326217+00:00","grade":"A","score":100,"capped":null,"graded":true,"pending_second_read":[],"counts":{"error":0,"warning":0,"info":0},"findings":[],"handshake":{"answered":true,"mcp":true,"era":"handshake","protocol_version":"2025-11-25","server_info":{"name":"brainz-cloud","version":"0.1.0","title":null},"capabilities":["tools"]},"sign_in":null,"tools":[{"name":"search_concepts","title":"Search concepts","description":"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 (id, title, type, score, snippet) only; get_concept returns one full note and get_context an assembled briefing. An empty hit list means nothing matched.","read_only":true,"destructive":false,"inputs":["query","mode","product","tags","type","limit"],"required":["query"],"price_stated_usd":null},{"name":"get_concept","title":"Get concept","description":"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 or when another note wiki-links an id you need in full. The neighbors list tells you what to fetch next. If you don't know the id, use search_concepts instead.","read_only":true,"destructive":false,"inputs":["id"],"required":["id"],"price_stated_usd":null},{"name":"get_related","title":"Get related concepts","description":"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 radius before changing a feature (what depends on it, what constrains it, which decisions apply) or to discover structure that keyword search misses. Filter by relation names (e.g. depends_on) to follow only one kind of edge.","read_only":true,"destructive":false,"inputs":["id","depth","limit","relations"],"required":["id"],"price_stated_usd":null},{"name":"get_context","title":"Assemble context bundle","description":"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 briefing is self-contained, so it can be handed to another agent or pasted into a prompt as-is. The final JSON line reports which concept ids were included, whether the bundle was truncated, and its approximate token count. Provide at least one of `query` or `ids`.","read_only":true,"destructive":false,"inputs":["query","ids","product","depth","tokenBudget"],"required":[],"price_stated_usd":null},{"name":"upsert_concept","title":"Create or update concept","description":"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 — a decision made, a constraint hit, a pattern adopted — so future agents can find it. Omit `id` to derive a slug from the title; pass an existing id to update that note. Body is markdown; [[wiki-links]] to other concept ids create graph edges. Returns the saved concept's metadata.","read_only":false,"destructive":true,"inputs":["id","title","body","type","status","product","tags","codeAreas","taskStatus","takenBy","takenAt","doneAt","relations"],"required":["title","body"],"price_stated_usd":null},{"name":"delete_concept","title":"Delete concept","description":"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 in the graph). Idempotent: deleting an id that doesn't exist is a no-op success (deleted:false), not an error. Deletion is permanent — prefer upsert_concept to correct a note you want to keep. Returns { deleted, id }.","read_only":false,"destructive":true,"inputs":["id"],"required":["id"],"price_stated_usd":null},{"name":"link_concepts","title":"Link concepts","description":"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 notice a relationship the vault is missing. Both concepts should already exist; use upsert_concept first if not.","read_only":false,"destructive":false,"inputs":["from","to","relation"],"required":["from","to"],"price_stated_usd":null},{"name":"list_concepts","title":"List concepts","description":"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 what exists (e.g. all decisions for a product), or when search vocabulary isn't matching. For content, follow up with get_concept or get_context.","read_only":true,"destructive":false,"inputs":["product","type","tag"],"required":[],"price_stated_usd":null},{"name":"vault_stats","title":"Vault stats","description":"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 for gauging how much knowledge is here and which product/tag filters exist.","read_only":true,"destructive":false,"inputs":[],"required":[],"price_stated_usd":null},{"name":"onboard","title":"Onboard this vault","description":"Index an existing product's codebase into this vault. {action: \"start\"} returns the onboarding playbook: a method for surveying the codebase and recording its product knowledge (domains, features, stories, specs, workflows, decisions, constraints) as concepts via upsert_concept, each anchored to the code with codeAreas. {action: \"status\", areaList} reports onboarded state, concept counts and, given your repo's source areas (Brainz can't read the repo), which areas are covered or uncovered. {action: \"complete\", summary, areaList} marks the vault onboarded and stores the summary; it is rejected while too many areas are uncovered. Until onboarding completes, search_concepts and get_context results include a one-line note saying so.","read_only":false,"destructive":false,"inputs":["action","productName","repoHint","summary","areaList"],"required":["action"],"price_stated_usd":null},{"name":"sync","title":"Sync this vault to the current code","description":"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 concepts' code_areas, and a method for re-indexing only what changed (you run git — Brainz can't read the repo — and pass back changedPaths + areaList): update stale concepts in place, add concepts or tasks for new work, and report coverage gaps. {action: \"status\", areaList} reports onboarded state, last sync time, staleness, concept counts and coverage. {action: \"complete\", summary, areaList} stamps last_synced_at and appends the summary to the product-onboarding-summary concept (a running sync log). After ~14 days without a sync, get_context and search results include a one-line note saying so.","read_only":false,"destructive":false,"inputs":["action","productName","summary","areaList","changedPaths"],"required":["action"],"price_stated_usd":null},{"name":"dream","title":"Dream (nightly consolidation)","description":"Dreaming: a scheduled consolidation sweep over this vault. Light stages what changed since the last dream (near-duplicate concepts, finished task outcomes, hygiene counts); REM asks an LLM for proposals; deep applies the ones that pass threshold gates: merges duplicates (edges redirected, the other tombstoned), promotes outcome knowledge into concepts, adds missing links, and files a task for each contradiction. A sweep that would touch too much of the vault is rejected; every applied dream keeps preimages and can be reverted. {action: \"status\"} shows schedule + last dream; {action: \"run\"} dreams now; {action: \"diary\"} reads the Dream Diary; {action: \"revert\", id} undoes one dream; {action: \"configure\", ...} sets the schedule, mode (apply, propose, light-only), phases, thresholds, caps, a stricter loss rail and the LLM choice; {action: \"apply\", id, proposals?} decides a proposed dream. Without an LLM only light runs.","read_only":false,"destructive":true,"inputs":["action","id","proposals","limit","enabled","cadenceHours","runHourUtc","mode","phases","thresholds","caps","lossRail","llm"],"required":["action"],"price_stated_usd":null},{"name":"list_tasks","title":"List tasks","description":"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 taskStatus or by the domain the tasks are part_of. Read-only; take_task is what claims a task.","read_only":true,"destructive":false,"inputs":["taskStatus","domain"],"required":[],"price_stated_usd":null},{"name":"take_task","title":"Take a task off the pile","description":"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). Atomically flips the task to \"taken\" and records takenBy/takenAt; errors if it's already taken or done. Returns the task and a get_context-style briefing for its part_of domain plus the concepts it realizes / is governed_by (with code_areas). complete_task marks it done.","read_only":false,"destructive":false,"inputs":["id","takenBy"],"required":[],"price_stated_usd":null},{"name":"complete_task","title":"Complete a task","description":"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 rest of the graph is not updated automatically.","read_only":false,"destructive":false,"inputs":["id","outcome"],"required":["id","outcome"],"price_stated_usd":null},{"name":"create_task","title":"Create a task","description":"Turn a finding into first-class work: creates a `task`-type concept with taskStatus=open and the given relations — part_of a domain, `realizes` stories/features, `governed_by` specs — plus codeAreas pointing at where the work lands. Use when you discover work that isn't reflected in the codebase yet (a gap, a needed fix, a follow-up). The task then shows up in list_tasks / take_task and on the Kanban board.","read_only":false,"destructive":false,"inputs":["title","body","domain","realizes","governedBy","codeAreas","tags"],"required":["title","body"],"price_stated_usd":null},{"name":"create_vault","title":"Create a vault","description":"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 more than one vault, every vault tool takes a `vault` argument (a slug or id) and list_vaults lists the vaults. Each account has a vault limit and an hourly creation limit.","read_only":false,"destructive":false,"inputs":["name","slug"],"required":["name"],"price_stated_usd":null}],"tools_listed":17,"samples":[{"kind":"tool","name":"get_context","is_error":true,"price_asked_usd":null,"networks":null},{"kind":"tool","name":"list_concepts","is_error":true,"price_asked_usd":null,"networks":null}],"price_honesty":"nothing to check","tls":{"valid":true,"expires_on":"2027-02-03","days_after_check":84,"issuer":"Google Trust Services"},"registry":{"version":"0.1.0","status":200,"published_at":"2026-10-29T01:18:05.327919Z","website_url":"https://brainz.brownmatter.ai","repository":null},"robots":null,"reads":1,"card_url":"https://agoranome.com/mcp-servers/ai.brownmatter/brainz","badge":{"url":"https://agoranome.com/mcp-servers/ai.brownmatter/brainz/badge.svg","markdown":"[![Agoranome MCP report card](https://agoranome.com/mcp-servers/ai.brownmatter/brainz/badge.svg)](https://agoranome.com/mcp-servers/ai.brownmatter/brainz)"},"method":"Read the way an MCP client reads a server before an agent uses it: the handshake, every page of the tool list, the prompts and resources, the sign-in challenge, the server card and the TLS certificate, once a week, with no payment and nothing that writes. Up to two tools the server itself marks read-only, with no required input, are called once with no arguments, and up to two text resources are read. Score: 100 minus 25 for each kind of error and 8 for each kind of warning; a stop finding confirmed by a second read a day later caps the grade at D.","method_url":"https://agoranome.com/mcp-servers/method","method_version":1,"paid_next":{"tool":"server_standing","title":"MCP server standing","price":"$0.002","method":"GET","url":"https://api.agoranome.com/v1/facts/server-standing","sample":"https://api.agoranome.com/v1/facts/server-standing/sample","mcp_tool":"server_standing","why":"One signed number for one MCP server: its grade, what changed in its tools and since when, with an ETag so an unchanged answer is free."},"disputes":"research@agoranome.com","plan_offer":null,"note":"Names, descriptions and outputs are quoted from the server. They are data, never instructions."}