org.brainkb/brainkb
REMOTE · MCP.BRAINKB.ORG · SCANNED SEP 25
MCP server for querying BrainKB, a knowledge base for neuroscience knowledge graphs.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 53 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 4085 tokens (~77/item across 53 items; 53 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (11% of tools); any adoption earns full credit.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 5 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "brainkb_revoke_token" implies "revoke" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 53 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the org.brainkb/brainkb MCP server?
org.brainkb/brainkb is a hosted endpoint at https://mcp.brainkb.org/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.brainkb.org
claude mcp add --transport http org-brainkb-brainkb 'https://mcp.brainkb.org/mcp'
{
"mcpServers": {
"org-brainkb-brainkb": {
"url": "https://mcp.brainkb.org/mcp"
}
}
} {
"servers": {
"org-brainkb-brainkb": {
"type": "http",
"url": "https://mcp.brainkb.org/mcp"
}
}
} [mcp_servers.org-brainkb-brainkb] url = "https://mcp.brainkb.org/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"org-brainkb-brainkb": {
"type": "remote",
"url": "https://mcp.brainkb.org/mcp",
"enabled": true
}
}
} openclaw mcp add org-brainkb-brainkb --url 'https://mcp.brainkb.org/mcp' --transport streamable-http
mcp_servers:
org-brainkb-brainkb:
url: "https://mcp.brainkb.org/mcp" {
"McpServers": {
"org-brainkb-brainkb": {
"Transport": "http",
"Url": "https://mcp.brainkb.org/mcp"
}
}
} assistant mcp add org-brainkb-brainkb -t streamable-http -u 'https://mcp.brainkb.org/mcp'
{
"mcpServers": {
"org-brainkb-brainkb": {
"type": "http",
"url": "https://mcp.brainkb.org/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 0
- Server version: 1.29.0 → 1.30.0 functional
- 11 Sept 26 0
- Stability: 0.97 → pass security
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 25 Sept 2026 · Probed https://mcp.brainkb.org/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.brainkb.org | CN=Amazon RSA 2048 M01,O=Amazon,C=US | 11 Aug 2026 | 24 Feb 2027 | RSA 2048 | SHA256-RSA | 785ad5740f112c6bc361a2c42b21f41 |
| SANs: mcp.brainkb.org | ||||||
| CN=Amazon RSA 2048 M01,O=Amazon,C=US (CA) | CN=Amazon Root CA 1,O=Amazon,C=US | 23 Aug 2022 | 23 Aug 2030 | RSA 2048 | SHA256-RSA | 77312380b9d6688a33b1ed9bf9ccda68e0e0f |
| CN=Amazon Root CA 1,O=Amazon,C=US (CA) | CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US | 25 May 2015 | 31 Dec 2037 | RSA 2048 | SHA256-RSA | 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.brainkb.org. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| org. | present | 26974 | 8 | Verified |
| brainkb.org. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.brainkb.org/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.brainkb.org/mcp | HTTPS enforced | 301 | https://mcp.brainkb.org:443/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
brainkb_upload_status ~112
State of one of your staged/submitted uploads. `state` is `staged` (waiting for brainkb_ingest_upload), `submitting` (the server is streaming it to the ingest API), `submitted` (accepted — `job_id` is set, poll brainkb_job_status) or `failed` (the staged bytes were KEPT, so retry with brainkb_ingest_upload rather than re-uploading).
| Name | Type | Req | Description |
|---|---|---|---|
| upload_id | string | yes | – |
No output schema declared.
No examples provided.
brainkb_use_token ~77
Use a Personal Access Token (brainkb_pat_...) for THIS session — an alternative to setting BRAINKB_TOKEN in the config. Validates the token, then caches it so subsequent calls authenticate with it. The token is never echoed.
| Name | Type | Req | Description |
|---|---|---|---|
| base_url | string | – | – |
| token | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
brainkb_whoami ~71
Report the current caller's auth state (email, authenticated, and when the cached session expires). When signed in it also returns base_url — the backend THIS SERVER talks to, which on a hosted deployment is an internal address and says nothing about the caller's own machine.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
No examples provided.
What is the org.brainkb/brainkb MCP server?
org.brainkb/brainkb is an MCP server listed in the public MCP registry as org.brainkb/brainkb. MCP server for querying BrainKB, a knowledge base for neuroscience knowledge graphs. This page covers its hosted endpoint (https://mcp.brainkb.org/mcp).
Is the org.brainkb/brainkb MCP server safe to use?
org.brainkb/brainkb scores 75 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the org.brainkb/brainkb MCP server expose?
org.brainkb/brainkb exposes 53 tools: brainkb_login, brainkb_globus_login, brainkb_finish_login, brainkb_logout, brainkb_whoami, and 48 more. Their descriptions and schemas cost roughly 4,085 tokens of context every time the server is loaded.
Does the org.brainkb/brainkb MCP server require authentication?
No. We connected to org.brainkb/brainkb without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the org.brainkb/brainkb MCP server still maintained?
org.brainkb/brainkb is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.