Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Nimbus BCI

PYPI · NIMBUS-MCP · 2 COMPONENTS

AI agents build, train, and analyze BCI/EEG pipelines: data, models, experiments, live sessions.

+4 this week 75 Trust /100

Last scanned (4 hours ago)

Scores higher than 71% of PyPI servers

Category Health and Science

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 1 of 22 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency32
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Licence could not be checked: the licence is declared in free text we could not match to a standard (SPDX) licence identifier, so we cannot tell whether it is OSI-approved.Unverified
  • Actively maintained (last published 1 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability81
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 10014 tokens (~158/item across 63 items; 63 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management46
  • Stability check failed: the tool surface changed between 0.11.0 and 0.14.17: 0 tool removals, 1 breaking changes, 20 additions. See how to fix → Fail
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 4 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 64 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Changelog

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.

  • 24 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
  • 23 Oct 26 −12
    • Malware scan: pass → unverified ▼ security
    • Schema quality: unverified → 100 ▲ functional
    • Package version: 0.14.15 → 0.14.17 functional
  • 22 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
  • 21 Oct 26 +1
    • Malware scan: unverified → pass ▲ security
    • Package version: 0.14.11 → 0.14.15 functional
  • 20 Oct 26 0
    • Malware scan: unverified → pass ▲ security
    • Package version: 0.14.8 → 0.14.11 functional
  • 19 Oct 26 −15
    • Malware scan: pass → unverified ▼ security
    • Stability: 0.27 → fail ▼ security
    • Package version: 0.14.4 → 0.14.8 functional
  • 18 Oct 26 0
    • Tool safety: pass → unverified ▼ security
    • Stability: 0.23 → unverified ▼ security
    • Tool coverage: 100 → unverified ▼ functional
    • Capabilities: pass → unverified ▼ functional
    • Destructive annotations: pass → 100 functional
    • Package version: 0.14.2 → 0.14.4 functional
  • 17 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

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 24 Oct 2026 · Analysed pypi/nimbus-mcp@0.14.17

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem pypi
Reason No attestation published

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted hatchling.build

Background: Why install scripts are a supply-chain risk →

Dependencies 22 packages
Packages resolved 22
Stale 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 63 exposed · ~8,987 tokens

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 →

Tool Tokens
protocol.pause ~59

Pause a running protocol session (blocks freeze; the session and device stay alive — resume with protocol.resume). Simulated and playback sessions only while paused: no data is recorded.

NameTypeReqDescription
session_idstringyesThe deploy session to pause.

Structured output declared, but exposes no named fields.

No examples provided.

protocol.resume ~98

Resume a paused protocol session (restarts the server-driven device loop). Live-hardware resume requires a Pro plan; simulated sessions are free. Pass the session's channel count (start_assignment reports it).

NameTypeReqDescription
chunk_sizeinteger–Samples per streamed chunk (default 125).
n_channelsinteger–Session channel count (the built-in template opens 4).
session_idstringyesThe deploy session to resume.

Structured output declared, but exposes no named fields.

No examples provided.

protocol.save ~84

Validate and persist the NEXT VERSION of a protocol document (confirm-gated: each call appends a version row; accidental calls clutter the version history). Edits create a new version — the assignment pins the version it runs.

NameTypeReqDescription
confirmboolean–MUST be true to write.
specobjectyesWire-format protocol document (validate first to iterate).

Structured output declared, but exposes no named fields.

No examples provided.

protocol.session_status ~84

Live snapshot of a protocol deploy session: the scheduler block / session progress + threshold state (under ``protocol``) beside the telemetry window (recent indicators, quality, stats).

NameTypeReqDescription
session_idstringyesThe deploy session to inspect (from start_assignment).
windowinteger–How many recent predictions to include (1-200, default 50).

Structured output declared, but exposes no named fields.

No examples provided.

protocol.start_assignment ~381

Enroll a subject and prepare their neurofeedback deploy session (confirm-gated — a session runs on a human). Creates the assignment (yoked sham arms REQUIRE yoked_donor_upload_id: a recorded simulated session's upload — mint one by running an active-arm session and data.upload-ing its recording), then persists the protocol graph as a deployable execution. Requires a Pro plan for LIVE hardware sessions; simulated-source sessions (the default template) are free. Graph source: execution_id reuses THAT run's stored graph (it must contain a protocol_session node; no device is pre-connected — the deploy session's data source stays yours). Without execution_id the built-in template graph is cloned — simulated source → bandpass → bandpower_indicator → protocol_session stamped with the protocol refs — and a simulated device is connected to the returned session id. The session starts when a client opens {statusUrl} (the deploy WS), sends init_deployment with modelExecutionId={executionId}, then start; the Studio app shows the feedback panel automatically. Poll protocol.session_status; stop with protocol.stop (the recording's block annotations + assignment progression are written on stop).

NameTypeReqDescription
armstringyesactive | sham.
confirmboolean–MUST be true — explicit go-ahead for a session on a human.
execution_id––Optional completed execution whose stored graph carries a protocol_session node; default clones the template.
protocol_idstringyesSaved protocol id (protocol.save).
protocol_versionintegeryesImmutable version the assignment pins.
subject_labelstringyesSubject identifier (e.g. "S01").
yoked_donor_upload_id––Donor recording upload (required when the arm's blocks resolve to yoked — the backend validates coverage).

Structured output declared, but exposes no named fields.

No examples provided.

protocol.stop ~74

Stop a protocol session (always safe to call): stops streaming, saves the block-annotated recording, advances the assignment when the scheduler reached its natural end, and disconnects the device (best-effort — a failed disconnect is reported, never raised).

NameTypeReqDescription
session_idstringyesThe deploy session to stop.

Structured output declared, but exposes no named fields.

No examples provided.

protocol.validate ~116

Validate a neurofeedback protocol document WITHOUT saving it. Returns {valid: true, spec} on success, or {valid: false, errors: [...]} with the per-violation list (loc/msg) when the document is invalid — the verdict is data, never an exception.

NameTypeReqDescription
specobjectyesWire-format protocol document (camelCase): id, name, indicator {name, transform}, armDefaults, blocks [{id, kind: assessment|training, durationSec, feedback?}], threshold, sessions, breakCriteria.

Structured output declared, but exposes no named fields.

No examples provided.

python.validate ~141

Statically check a python_model script (BYO model class) without running it. Compiles the source and verifies the contract — a class with fit(X, y, info) and predict(X); optional predict_proba(X) unlocks confidence panels. Never executes the code, so it is safe against the hosted backend. Use it before execution.run to catch syntax errors, missing methods, or the wrong class name cheaply.

NameTypeReqDescription
class_name––Contract class to instantiate; omit to auto-detect the first class defining fit+predict.
codestringyesPython source of the model class (<=256KB UTF-8).

Structured output declared, but exposes no named fields.

No examples provided.

stats.grouped ~352

Cluster-aware group statistics across executions. REQUIREMENT (read first): each execution must have been run with an evaluation plan that STORED per-SUBJECT accuracies for at least 3 subjects — e.g. leave-one-subject-out (LOSO) or grouped CV over >= 3 subjects. Session groups within one subject (multi-session single-subject runs) are refused with ``nimbus.stats.non_subject_groups`` — those are not independent subjects. A plain single-subject CV run with no subject/session grouping stores no group stats and fails with ``nimbus.stats.insufficient_groups``. What it does: pools the per-subject accuracies each run's evaluation plan stored, then reports the between-group summary — mean accuracy with a t-interval and a one-sample t-test vs chance. Responses label ``groupKind``, real ``groupKeys`` (subject ids like S01 when stamped or recoverable), ``perGroup`` (key + accuracy pairs), ``overall.pooledExecutionIds``, and ``kindBreakdown`` / ``overall.kindBreakdown`` (per_subject vs loso etc. with n + mean — #470; between-group pooled mean is unchanged).

NameTypeReqDescription
chance––Chance level in [0, 1]; default 1/nClasses per execution.
execution_idsarrayyes1–25 executions (from execution.run) to pool. Runs without subject group stats are reported with nulls but do not fail the request — unless NONE qualifies (``nimbus.stats.insufficient_groups``) or on…

Structured output declared, but exposes no named fields.

No examples provided.

stream.start ~331

Connect an EEG device and START a live streaming session on the user's head. Requires confirm=True; call device.test first. Track with stream.status(). Idle watchdog: if no stream.status()/stream.telemetry() poll happens for idle_timeout_sec (default 900), the session is stopped and the device disconnected automatically — an abandoned stream never keeps running on the user's head. Any poll resets the timer; idle_timeout_sec=0 disables the watchdog.

NameTypeReqDescription
chunk_sizeinteger–Samples per streamed chunk (default 125).
confirmboolean–MUST be true to start — the explicit user go-ahead for a live session on their head; anything else is refused with zero requests.
connection_type––Device-specific selector (e.g. serial vs wifi).
device_typestringyesDevice id from device.list (e.g. "brainbit").
idle_timeout_secinteger–Watchdog: stop+disconnect after this many seconds without a status poll (default 900; 0 disables).
ip_address––Device IP for network/wifi devices.
ip_port––Port for network devices.
mac_address––Bluetooth MAC (BT devices).
n_channelsinteger–Channel count to open (default 8).
port––Serial/COM port for wired devices.
serial_number––Device serial (some BLE stacks).
session_id––Optional existing session to resume/reuse.
source_id––LSL source id.
stream_name––LSL stream name (LSL devices).

Structured output declared, but exposes no named fields.

No examples provided.

stream.status ~59

Live snapshot of a streaming session (running, deviceConnected). Polling this also feeds the idle watchdog: each call resets the session's idle timer (see stream.start's idle_timeout_sec).

NameTypeReqDescription
session_idstringyesThe streaming session to inspect.

Structured output declared, but exposes no named fields.

No examples provided.

stream.stop ~53

Stop a streaming session and disconnect the device (always safe to call). Also removes the session from the idle watchdog so it cannot fire after an explicit stop.

NameTypeReqDescription
session_idstringyesThe streaming session to stop.

Structured output declared, but exposes no named fields.

No examples provided.

stream.telemetry ~197

Live snapshot of a streaming session: latest prediction + recent window, signal quality (meanChannelQuality, snrDb, artifactProbability), indicators, running stats. Poll this while a session runs. Works with OR without a deployed model: modelless hardware streams (no classifier) report live signal quality + focus/relaxation band-power indicators with latestPrediction null; deployed sessions additionally carry predictions and confidence stats. Expect low confidence during filter/ASR warm-up (first seconds); quality < 0.5 or high artifactProbability means the signal is poor. 404 => session not active in this backend. Each poll also feeds the idle watchdog (see stream.start's idle_timeout_sec), keeping an actively watched session alive.

NameTypeReqDescription
session_idstringyesThe streaming session to read telemetry for.
windowinteger–How many recent predictions/chunks to include (default 50).

Structured output declared, but exposes no named fields.

No examples provided.

Install

How do I install the Nimbus BCI MCP server?

Nimbus BCI runs locally as a PyPI package, launched with uvx nimbus-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · nimbus-mcp

# add to Claude Code
claude mcp add nimbusbci-nimbus-mcp -- uvx nimbus-mcp
Common questions

What is the Nimbus BCI MCP server?

Nimbus BCI is an MCP server listed in the public MCP registry as io.github.nimbusbci/nimbus-mcp. AI agents build, train, and analyze BCI/EEG pipelines: data, models, experiments, live sessions. This page covers its PyPI package (nimbus-mcp).

Is the Nimbus BCI MCP server safe to use?

Nimbus BCI scores 75 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 24 October 2026. 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 Nimbus BCI MCP server expose?

Nimbus BCI exposes 63 tools: account.whoami, catalog.nodes, catalog.node_schema, catalog.templates, catalog.template, and 58 more. Their descriptions and schemas cost roughly 8,987 tokens of context every time the server is loaded.

Is the Nimbus BCI MCP server still maintained?

Nimbus BCI is still listed as active in the MCP registry. We last reached this channel on 24 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.