Ext Ops Panel
Open dashboard
Comparison

bci vs Nimbus BCI

bci is a plugin bundle for AI coding tools published by qinnovates. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Nimbus BCI is an MCP server published by nimbusbci. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). As of our marketplace pass on 2026-10-28. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplacebciNimbus BCI
Claude Code: claude-plugins-community Listed
Version: 1.1.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.14.17
Downloads/month (PyPI): 1 355
Downloads/week (PyPI): 1 864
Forks (GitHub): 0
Stars (GitHub): 3
Not marked · First seen
PyPI (MCP servers) Not listed Listed
Version: 0.14.17
Downloads/month (PyPI): 1 355
Downloads/week (PyPI): 1 864
Forks (GitHub): 0
Stars (GitHub): 3
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

bci vs Nimbus BCI
FactbciNimbus BCI
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)0 (worse)3 (better)
Forks (GitHub)00
Last release (differs)Not published2026-10-23
Where it runs (differs)Installs as a plugin bundleRemote server or your machine
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published5, secrets among them: 2
Hooks it runs (differs)1Not published
Parts of the bundle (differs)12Not a bundle
Licence (differs)Apache-2.0 (code), CC-BY-4.0 (data)Not stated
Repository (differs)github.com/qinnovates/bci-securitygithub.com/nimbusbci/nimbus-mcp
Changes in the last 7 days (differs)02
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded less than an hour ago, requires a key

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

bci

In its own words, on Claude Code: claude-plugins-community:

The first BCI toolkit for researchers, developers, and security engineers. Threat modeling, vulnerability scoring, pattern detection, and neuroethics compliance for brain-computer interfaces. Reports are built with privacy by design and auto-redact PII. Please see Github README before use.

Nimbus BCI

In its own words, on Official MCP Registry:

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

How to run each

bci As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install bci@claude-community

Nimbus BCI As a remote MCP server

Claude Code
claude mcp add --transport http nimbus-mcp https://nimbus-mcp.fly.dev/mcp

Requires: NIMBUS_MCP_KEY (secret), NIMBUS_TOKEN (secret)

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only Nimbus BCI has a remote endpoint we check. How we check endpoints

Tools each declares

Neither the marketplaces of bci nor its endpoint list any tools, so we do not compare tools.

Settings each asks for

The marketplaces of bci publish no settings it asks for, so we do not compare settings.

What it can do: bci · What it can do: Nimbus BCI · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the Python Package Index (pypi.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built