mcp-registry/org.brainkb/brainkb · v1.30.0
As of 2026-10-26 22:33 UTC, the Brainkb MCP server is up with a Glimind reliability score of 86/100 (grade B). Over the last 30 days it answered 99.8% of Glimind's liveness checks. It had 6 outages in 90 days, with a median recovery of 2 minutes.
MCP server for querying BrainKB, a knowledge base for neuroscience knowledge graphs.
Point your MCP client at this streamable-http endpoint: https://mcp.brainkb.org/mcp
72 of 72 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
72 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.
Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →
158 parameter(s) across 61 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
13 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
In the last 30 days: 2 tool(s) removed and 12 schema change(s).
Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 61 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Forg.brainkb%2Fbrainkb/fixes
{
"name": "brainkb_add_access_rule",
"description": "(Space manager) Restrict a space action to a subject.\n action: 'read' | 'write' | 'manage'.\n subject_type: 'global_role' (e.g. 'Admin','Lab Member') | 'member' (an email) |\n 'space_role' ('viewer'|'editor'|'owner', matched as >=).\n When rules exist for an action, only matching callers may perform it; the space\n owner and Admin/SuperAdmin always bypass (no lockout). Example: restrict writing\n to Admins -> action='write', subject_type='global_role', subject_value='Admin'.",
"inputSchema": {
"type": "object",
"title": "brainkb_add_access_ruleArguments",
"required": [
"slug",
"action",
"subject_type",
"subject_value"
],
"properties": {
"slug": {
"type": "string",
"title": "Slug"
},
"action": {
"type": "string",
"title": "Action"
},
"subject_type": {
"type": "string",
"title": "Subject Type"
},
"subject_value": {
"type": "string",
"title": "Subject Value"
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}{
"name": "brainkb_add_space_graph",
"description": "Register a named graph and bind it to a space, so ingest/read on that graph\n are governed by the space's membership and visibility. Owner/editor only.\n The named_graph_iri is **globally unique** — one graph belongs to exactly one\n space. If it's already registered (to any space) the call returns 409; graph\n bindings are permanent (no unregister/delete).",
"inputSchema": {
"type": "object",
"title": "brainkb_add_space_graphArguments",
"required": [
"slug",
"named_graph_iri"
],
"properties": {
"slug": {
"type": "string",
"title": "Slug"
},
"description": {
"type": "string",
"title": "Description",
"default": ""
},
"named_graph_iri": {
"type": "string",
"title": "Named Graph Iri"
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}{
"name": "brainkb_add_space_member",
"description": "Add/update a space member. role: 'owner' | 'editor' | 'viewer'. Owner only.",
"inputSchema": {
"type": "object",
"title": "brainkb_add_space_memberArguments",
"required": [
"slug",
"member_email"
],
"properties": {
"role": {
"type": "string",
"title": "Role",
"default": "viewer"
},
"slug": {
"type": "string",
"title": "Slug"
},
"member_email": {
"type": "string",
"title": "Member Email"
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/org.brainkb/brainkb"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/org.brainkb/brainkb"}) over MCP.
brainkb_synthscholar_studies ~363 tokensbrainkb_synthscholar_screening ~342 tokensbrainkb_synthscholar_records ~298 tokensbrainkb_create_space ~287 tokensbrainkb_update_space ~271 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Forg.brainkb%2Fbrainkb?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Forg.brainkb%2Fbrainkb?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Forg.brainkb%2Fbrainkb.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Forg.brainkb%2Fbrainkb.svg :target: https://glimind.com/server/mcp-registry%2Forg.brainkb%2Fbrainkb?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:5cc3d836c25f24aa…, first seen 2026-10-21, included at leaf 40714 of 75,845. Version history · verify what your client received.
Compare: most reliable admin servers · most reliable security servers · most reliable knowledge servers · most reliable database servers · most reliable data servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-26 22:33 UTC, the Brainkb MCP server is up with a Glimind reliability score of 86/100 (grade B). Over the last 30 days it answered 99.8% of Glimind's liveness checks. It had 6 outages in 90 days, with a median recovery of 2 minutes.
Brainkb MCP server advertises 72 tools, including brainkb_activate_user, brainkb_add_access_rule, brainkb_add_space_graph, brainkb_add_space_member, brainkb_assign_role.
Point your MCP client at this streamable-http endpoint: https://mcp.brainkb.org/mcp
Glimind scanned all 72 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.