Saltar al contenido
Logo de BrainKB

Servidor MCP de BrainKB

Qué servidores MCP son de BrainKB, del registro oficial y encontrados preguntando a su propio dominio, si responden y qué ofrecen. Un programa comprobó cada dato; nada está copiado de la página del producto.

leído el 2026-10-26

← Volver a BrainKB

De quién es el servidor
  • Nombre en el registroorg.brainkb/brainkbverificado en el registro MCP

El nombre en el registro está bajo brainkb.org. El registro solo permite usar ese espacio de nombres a quien demuestra control del dominio por DNS o HTTP.

Cuando le preguntamoscomprobado el 2026-10-26
  • Estadorespondecomprobado el 2026-10-26
  • Herramientas72
  • El servidor se llamabrainkb
  • Versión del servidor1.30.0
  • Versión del protocolo2025-06-18

El 2026-10-26 el servidor respondió a initialize y tools/list sin iniciar sesión. Primera respuesta en 234 ms.

¿Debe un agente conectarlo?Aún no está claro
  • Sus herramientas hacen Query neuroscience findings in a shared knowledge graph, pero no Browse abstracts with semantic search on a UMAP map; Convert meeting recordings into decisions and action items.
  • Comprobado 2 de los 7 días necesarios para juzgar su fiabilidad.

Una vez conectado

  • Para "Query neuroscience findings in a shared knowledge graph", la primera llamada probable es brainkb_search.
  • brainkb_create_token, brainkb_create_space, brainkb_set_space_visibility, brainkb_update_space, brainkb_delete_space cambian datos sin iniciar sesión: cualquiera con la dirección puede llamarlas.
  • Parámetros sin tipo o sin descripción en 61 de 72 herramientas: revisa los argumentos antes de llamar.

Lo dicen reglas a partir de las mediciones de arriba. La primera llamada probable la elige un modelo de la lista de herramientas; lee su descripción antes de fiarte.

Medido cada díacomprobaciones diarias: 2, la primera el 2026-10-26
  • Nota INITE MCPtras una semanala nota necesita 7 comprobaciones diarias: 2 hasta ahora
  • Qué puede hacer un agente con él1 de 3 casos de uso
  • Uso6 estrellas en GitHub
  • Respondiómidiendo2 de las 7 comprobaciones diarias necesarias para mostrar el porcentaje
  • Mediana de la primera respuesta244 ms
  • Espacio en el contexto del agente≈ 10.827 tokenslas definiciones de todas sus herramientas (72), que el agente lleva en cada turno
  • Definiciones de herramientasC · 69 de 100
  • Resultados tipados6 de 72 herramientasdeclaran outputSchema: el resultado llega tipado y se lee de una vez
  • Parámetros sin descripción: en 61 de 72
  • Sin indicar si solo lee o puede destruir: 72 de 72

Qué puede hacer un agente con él

  • puede · Query neuroscience findings in a shared knowledge graph
  • no puede · Browse abstracts with semantic search on a UMAP map
  • no puede · Convert meeting recordings into decisions and action items

Cada caso de uso del producto se le preguntó a Jev junto con la lista de herramientas de este servidor: ¿puede un agente hacerlo con estas herramientas?

Conviene revisar

  • Herramientas que cambian datos, en un servidor que responde sin iniciar sesión: brainkb_create_token, brainkb_create_space, brainkb_set_space_visibility, brainkb_update_space, brainkb_delete_space

Un programa comprueba el servidor una vez al día: initialize y tools/list, sin modelo. Los tokens son la longitud de las definiciones, a unos cuatro caracteres por token. La nota promedia seis comprobaciones del nombre, la descripción, el esquema y las anotaciones de cada herramienta; dice lo bien descritas que están, no si funcionan. La nota pondera solo lo medido: si responde (25%), si hace el trabajo del producto (25%), definiciones (20%), contexto (10%), uso (10%) y lo fácil que es conectarse (10%). Lo que no se midió queda fuera, y una instrucción oculta limita la nota a 40. El estado de los servidores MCP de los proveedores: método y números →

Herramientas que ofrece72 herramientas · leído el 2026-10-26
  • 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…

  • 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…

  • 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…

  • 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…

  • 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…

  • 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…

  • 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…

  • 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…

  • 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…

  • 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…

  • 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…

  • 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…

  • 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…

  • 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…

  • 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…

  • 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…

  • 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)…

  • 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…

  • 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…

  • 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…

  • 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…

  • 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…

  • 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_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…

  • 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…

  • 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…

  • 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…

  • 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…

  • 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…

Las primeras 60 de 72, en el orden del servidor.

Cómo conectar

Añade el servidor a la configuración de tu cliente MCP. Claude Desktop, Cursor y la mayoría de los demás clientes leen este formato:

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

Añadirlo

Claude Code, en una terminal

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

Añadir a CursorAñadir a VS Code

claude.ai, ChatGPT y otros clientes: añade https://mcp.brainkb.org/mcp como conector personalizado en los ajustes.

Cada línea es algo que un programa encontró al buscar: la entrada del registro, la respuesta del propio servidor, una especificación que se puede leer. Si falta una línea, es que no la encontramos, no que no exista.