List your agent

brainkb

MCP server● Hosted · onlinev0.1.0

MCP server for querying BrainKB, a knowledge base for neuroscience knowledge graphs

What you can do with it

Share of each task's required capabilities it covers

Prefer a ready-made agent?

An MCP server is a connector for your own assistant. These finished products do the job for you: answer customer questions.
All AI agents to answer customer questions, ranked →

Similar tools

Listed for the same task: answer customer questions

Reviews

No review yet. Used brainkb? Be the first to help others choose.

What it does

brainkb is an MCP server, a connector that lets an AI assistant use it as a tool. It is hosted: an assistant connects to it over the internet, nothing to install.

From the publisher's description, Electra Index matched it to one capability: knowledge base qa. That makes it a candidate for tasks such as answer customer questions or answer questions from internal documents.

Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.

At a glance

Hosted (remote)YES
Local installNO
Version0.1.0
PriceNot in the registry
First seen26 Sept 2026
Last checked21h ago

How to connect

As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 12h ago (live check)

Hosted endpoint

  • https://mcp.brainkb.org/mcp streamable-http

In Claude Code: claude mcp add --transport http brainkb https://mcp.brainkb.org/mcp

MCP settings (Claude Desktop, Cursor and other MCP clients)

{
  "mcpServers": {
    "brainkb": {
      "url": "https://mcp.brainkb.org/mcp"
    }
  }
}

Live check

Electra Index connected to the hosted endpoint 12h ago

ONLINE brainkb answered an MCP connection on 16 Nov 2026 and introduced itself as brainkb 1.30.0 (MCP protocol 2025-06-18).

72 tools offered to AI assistants

  • brainkb_login · Authenticate to BrainKB with the user's credentials and cache the JWT for THIS session only (isolated per caller). The password/token are never echoed. Uses single sign-on: one login mints a refresh token, cached for THIS session, which is
  • brainkb_globus_login · Start an OAuth login (Globus / ORCID / GitHub) for THIS session — use this instead of brainkb_login when the user signs in with Globus rather than a password. Returns a URL to open in a browser; after signing in, the page shows a short one-
  • brainkb_finish_login · Complete an OAuth login started with brainkb_globus_login by exchanging the one-time code shown in the browser for a session token. The code is single-use and never echoed back.
  • brainkb_logout · Forget the cached token for this session.
  • brainkb_whoami · 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 not
  • brainkb_create_token · Generate a Personal Access Token (PAT) for browser-free auth. Requires you to be logged in already (brainkb_login or brainkb_globus_login). The token is shown ONCE and never again — copy it and set it as BRAINKB_TOKEN in your MCP/skill conf
  • brainkb_list_tokens · List your Personal Access Tokens (metadata only — the secret is never shown): id, name, prefix, created/last-used/expiry, and whether each is active/revoked/expired. Use the id with brainkb_revoke_token.
  • brainkb_revoke_token · Revoke one of your Personal Access Tokens by id (see brainkb_list_tokens). Takes effect immediately — the next call using that token fails.
  • brainkb_use_token · 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.
  • brainkb_list_spaces · List spaces the user can see (their own/member spaces + public ones), each annotated with THIS caller's permission so you know what they may do: - your_role: 'owner' | 'editor' | 'viewer' | null (their space membership, including a role inh
  • brainkb_create_space · Create a workspace/space, or a subspace inside one. The caller becomes owner. slug: lowercase/hyphen id, **globally unique** — if it's already taken the call returns 409 (pick another slug). visibility: 'private' or 'public' (set per space:
  • brainkb_get_space · A space's details: graphs, members (direct, plus `inherited_members` with the parent space each comes from), visibility, `parent_slug`, `ancestors` (root first) and direct `subspaces` — only the ones the caller may see — and the caller's `y
Show 60 more
  • brainkb_space_tree · A space and every subspace below it (any depth), nested: each node has slug, name, visibility, the caller's role and whether it's inherited from a parent, and its graph count. Only subspaces the caller may see are included.
  • brainkb_set_space_visibility · Set a space 'public' (anyone, even anonymous, can read) or 'private' (members only). Owner only. Everything in a public space is public: making a space public also makes all its subspaces public, and a subspace of a public space cannot be m
  • brainkb_update_space · Rename a space, change its description, and/or give it a new slug. Owner/manager only. Pass only what changes; description="" clears it. `new_slug` (lowercase letters, digits and hyphens, 3-64 chars) moves the space's IRI and every graph wh
  • brainkb_delete_space · PERMANENTLY delete a space and everything in it. SuperAdmin only; irreversible. Drops the space's named graphs and the ingestion-history (delta) graphs that hold copies of their data, removes the graphs' registry entries and the space's RDF
  • brainkb_add_space_member · Add/update a space member. role: 'owner' | 'editor' | 'viewer'. Owner only.
  • brainkb_add_space_graph · Register a named graph and bind it to a space, so ingest/read on that graph are governed by the space's membership and visibility. Owner/editor only. The named_graph_iri is **globally unique** — one graph belongs to exactly one space. If it
  • brainkb_ingest_text · Ingest raw RDF text (Turtle / N-Triples / JSON-LD, auto-detected) into a named graph. Returns a job_id; ingestion runs in the background — poll with brainkb_job_status. The graph must be registered (see brainkb_add_space_graph) and the call
  • brainkb_list_uploads · List RDF files YOU have staged with POST /upload but not yet ingested. Shows each upload_id, its size, sha256 and when it expires. Only your own uploads are visible.
  • brainkb_upload_status · 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 `faile
  • brainkb_discard_upload · Delete one of your staged uploads without ingesting it.
  • brainkb_ingest_upload · Ingest a file you staged with `POST /upload` into a named graph. This is the route for a large local file: your HTTP client streams the bytes straight to this server over HTTPS, then you name the resulting upload_id here. The server reads i
  • brainkb_ingest_files · Ingest local RDF files (ttl/nt/nq/rdf/owl/jsonld/json) into a named graph. Returns a job_id; runs in the background — poll with brainkb_job_status.
  • brainkb_synthscholar_ingest · Ingest a SynthScholar review — the output directory of a run (the folder holding review.json and review.ttl, as the synthscholar skill writes it) — into a space you may write to (see brainkb_list_writable_spaces; you need to be its owner or
  • brainkb_synthscholar_list_reviews · Ingested SynthScholar reviews you can read (public spaces: anyone): id, title, research question, space, graph, included count, when ingested, ingest job. `q` filters on text in the title or research question.
  • brainkb_synthscholar_studies · The included studies of an ingested review, filtered. `q`: text in title, authors, journal, DOI, PMID or keywords. `full_text`: true = read in full, false = abstract only. `source`: full-text route (europe_pmc, unpaywall, ezproxy, arxiv, …)
  • brainkb_synthscholar_screening · The screening audit trail of an ingested review: every decision with its stage (title_abstract | full_text), decision (include | exclude), what it was judged on (title_abstract | full_text | abstract_only), the full-text route and the reaso
  • brainkb_synthscholar_evidence · Evidence spans of an ingested review: the quoted text its claims rest on, with the study, section, relevance, and whether the quote was matched verbatim in the source (`grounded`). Filter by text, claim type, PMID or grounding.
  • brainkb_synthscholar_records · Per-study records an ingested review produced. `kind`: `charting` (the data-charting form's answers per study), `appraisal` (critical appraisal by domain) or `narrative` (narrative synthesis rows: design, methods, outcomes, limitations). `q
  • brainkb_synthscholar_text · An ingested review's own text: `abstract`, `introduction`, `synthesis`, `bias`, `limitations`, `conclusions`, `research_question`, `search_queries` or `per_group` (the per-group analysis) — or all of them when `section` is empty.
  • brainkb_synthscholar_find_study · Which ingested reviews (that you can read) include or screened a study — by DOI, PMID or part of its title (6+ characters) — and what happened to it in each: included (read in full or from the abstract) or each screening decision with its r
  • brainkb_synthscholar_get_review · One ingested review: summary, its graph and space, the files kept (path, kind, media type, size, sha256), the run's search log and verification, the screening basis and full-text retrieval. Long texts and the per-study list are left out her
  • brainkb_list_jobs · List the user's ingest jobs (newest first) with status and progress.
  • brainkb_job_status · Detailed status of one ingest job: status, progress %, current file/stage, per-file failures, and (when complete) a summary.
  • brainkb_recover_job · Attempt to recover a stuck/errored ingest job (marks it recoverable/errored).
  • brainkb_search · Full-text search over the knowledge graphs, access-filtered by space visibility. Pass `space` to scope to one workspace, omit for a full search. No login needed: an unauthenticated caller searches public spaces only. Anonymous/other users n
  • brainkb_read_space · Read all RDF (JSON-LD) in a space's graphs. Public spaces are readable by anyone without logging in (read-only); private spaces require login and membership. Don't ask the user to log in just to read a public space.
  • brainkb_list_writable_spaces · Spaces the caller can ingest into, each with its graphs (and descriptions) and `parent_slug` for subspaces — decided by the same checks ingestion uses: owner/ editor membership (including a role inherited from a parent space), a space write
  • brainkb_list_registered_graphs · List registered named graphs visible to the caller (private-space graphs the caller can't access are hidden).
  • brainkb_sparql · Run an arbitrary SPARQL query. Requires an Admin/SuperAdmin role (the sparql_admin capability) — for ordinary questions prefer brainkb_search, brainkb_read_space, or the provenance/delta tools, which need no admin role. Large results come b
  • brainkb_qa_list · Find a canned question BrainKB can answer, then run it with brainkb_qa_run. Prefer these over writing SPARQL: they are vetted against BrainKB's actual vocabulary. Discovery is two steps, so you never read every query at once: 1. brainkb_qa_
  • brainkb_qa_run · Run a canned question from brainkb_qa_list by id. `params` maps parameter names to values; they are validated and escaped, never spliced in raw. Runs through the same SPARQL endpoint as brainkb_sparql, so it needs the same role. Results pag
  • brainkb_provenance_job · PROV-O provenance bundle (JSON-LD) for one ingest job.
  • brainkb_provenance_graph · PROV-O ingestion/activity history (JSON-LD) for a named graph.
  • brainkb_delta · The exact triples a job added (its delta), as JSON-LD.
  • brainkb_delta_history · A named graph's change history: one entry per ingest delta (job, triple count, timestamp), newest first.
  • brainkb_delta_compare · Compare two jobs' deltas: A-only / B-only / shared triple counts + triples.
  • brainkb_capabilities · (Admin only) Show a user's roles, effective capabilities, and delegated grants. Useful to check why someone can/can't create team spaces, ingest, etc.
  • brainkb_grant_capability · (Admin only) Delegate a capability to a user — e.g. 'create_team_space' or 'manage_team_space' so a Curator/Lab Member can create/manage team spaces. Grantable: create_private_space, create_team_space, manage_team_space, ingest, recover, re
  • brainkb_revoke_capability · (Admin only) Revoke a previously granted capability from a user.
  • brainkb_list_capabilities · (Admin only) Catalog of all KG capabilities, which are delegatable ('grantable'), which are admin-only, and a description of each. Use this to see the available permission options before granting to a user or group/role.
  • brainkb_role_capabilities · (Admin only) List the capabilities granted to a role/group (e.g. 'uk_collaborator', 'Lab Member').
  • brainkb_grant_role_capability · (Admin only) Grant a capability to a whole role/group so EVERY member gets it — e.g. give a custom group 'uk_collaborator' the 'ingest' or 'create_private_space' capability. Grantable: create_private_space, create_team_space, manage_team_sp
  • brainkb_revoke_role_capability · (Admin only) Revoke a capability from a role/group.
  • brainkb_list_access_rules · List a space's fine-grained access rules (member/manager of the space).
  • brainkb_add_access_rule · (Space manager) Restrict a space action to a subject. action: 'read' | 'write' | 'manage'. subject_type: 'global_role' (e.g. 'Admin','Lab Member') | 'member' (an email) | 'space_role' ('viewer'|'editor'|'owner', matched as >=). When rules e
  • brainkb_remove_access_rule · (Space manager) Delete a fine-grained access rule by its id (see brainkb_list_access_rules).
  • brainkb_list_reserved_graphs · (Admin/SuperAdmin) List reserved named graphs: graph IRIs, or every IRI under a prefix, that only an Admin/SuperAdmin — or, when reserved for a space, that space's managers/editors — may register or bind. Includes the built-in system reserv
  • brainkb_reserve_graph · (Admin/SuperAdmin) Reserve a named graph so other users can't create it. match_type 'exact' reserves one graph IRI; 'prefix' reserves every IRI starting with it (e.g. 'https://brainkb.org/graph/allen/'). Give a `reason` — it is shown to any
  • brainkb_unreserve_graph · (Admin/SuperAdmin) Remove a reservation by its id (see brainkb_list_reserved_graphs). System reservations cannot be removed.
  • brainkb_list_users · (Admin) List users (profiles) — filter by `q` (name/email/orcid) or `role`. Shows profile_id, email, roles, providers, ban status.
  • brainkb_available_roles · (Admin) List the available roles/groups (Admin, Lab Member, Curator, …).
  • brainkb_create_role · (Admin) Create a new role/group — e.g. an 'External' collaborator group — which can then be assigned with brainkb_assign_role.
  • brainkb_assign_role · (Admin) Assign a role/group to a user by email (e.g. 'Lab Member', 'External', or a custom group). The user must already have a profile (created on first login/registration). NOTE: assigning the 'Admin'/'SuperAdmin' role is SuperAdmin-only
  • brainkb_remove_role · (Admin) Remove a role/group from a user by email.
  • brainkb_activate_user · (Admin) Activate a user's account (sets the JWT user active) by email.
  • brainkb_deactivate_user · (Admin) Deactivate a user's account by email.
  • brainkb_ban_user · (Admin) Ban a user by email (reversible; preserves history). This is how accounts are removed — there is NO hard delete. Banning an Admin is SuperAdmin-only; SuperAdmin accounts cannot be banned.
  • brainkb_unban_user · (Admin) Lift a ban on a user by email.
  • brainkb_list_permissions · (Admin) List all usermanagement permissions (resource/action pairs used for page-access and role-permission mapping). These are the addable 'permission' options; KG action-capabilities are listed by brainkb_list_capabilities.
  • brainkb_create_permission · (Admin) Create a new usermanagement permission, e.g. name='dataset.export', resource='dataset', action='export'. Attach it to roles via the usermanagement role-permissions API.

What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method

Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.

Facts & evidence

Each fact shows where it was seen and when.
FactValueEvidenceSourceLast confirmed
Hosted endpointhttps://mcp.brainkb.org/mcpDECLAREDSRC-001 Official MCP Registry21h ago
Local install (package)noDECLAREDSRC-001 Official MCP Registry21h ago
Remote access (hosted)yesDECLAREDSRC-001 Official MCP Registry21h ago
Repositoryhttps://github.com/sensein/BrainKBDECLAREDSRC-001 Official MCP Registry21h ago
Registry statusactiveDECLAREDSRC-001 Official MCP Registry21h ago
Version0.1.0DECLAREDSRC-001 Official MCP Registry21h ago
MCP serveryesDECLAREDSRC-001 Official MCP Registry21h ago

Change history

Baseline
No change detected yet. History builds up as the robots revisit this server.

Is this page accurate?

Flag it and our robot re-checks the official source. Reports never change a score.

Do you run brainkb? Know when it stops answering

For publishers · optional

Its hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.

Monitor brainkbLaunch offer $39.99 once, for life instead of $9.99/month · All plans

Monitoring never changes a score or a rank.

Are you the publisher of brainkb?

Free · show your listing

An independent listing builds trust with your buyers. Announce it, and add the badge to your website or README.

Announce it on LinkedIn
Listed on Electra IndexListed on Electra Index
<a href="https://electraindex.com/mcp/brainkb?utm_source=badge&utm_medium=share&utm_campaign=listing"><img src="https://electraindex.com/api/badge/brainkb/card" width="260" height="72" alt="Listed on Electra Index"></a>

Questions about brainkb

How do I connect brainkb?

Use the hosted endpoint https://mcp.brainkb.org/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.

What tools does brainkb offer?

When Electra Index connected on 16 Nov 2026, it listed 72 tools: brainkb_login, brainkb_globus_login, brainkb_finish_login, brainkb_logout, brainkb_whoami, brainkb_create_token, brainkb_list_tokens, brainkb_revoke_token and more. The full list is in "Live check" above.

Is brainkb online?

Yes. Its hosted endpoint answered an MCP connection from Electra Index 12h ago.

What can I use brainkb for?

Based on its description, it is most relevant to: answer customer questions, answer questions from internal documents, answer support phone calls, build a help center.