Ext Ops Panel
Open dashboard
Comparison

io.github.brain-bbqs/neuro vs io.github.daedalus/mcp-numpy

io.github.brain-bbqs/neuro is an MCP server published by brain-bbqs. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.daedalus/mcp-numpy is an MCP server published by daedalus. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-16. 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
Marketplaceio.github.brain-bbqs/neuroio.github.daedalus/mcp-numpy
Official MCP Registry Listed
Version: 1.0.0
Downloads/month (npm): 315
Downloads/week (npm): 43
Not marked · First seen
Listed
Version: 0.1.0
Downloads/month (PyPI): 60
Downloads/week (PyPI): 30
Forks (GitHub): 0
Stars (GitHub): 0
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

io.github.brain-bbqs/neuro vs io.github.daedalus/mcp-numpy
Factio.github.brain-bbqs/neuroio.github.daedalus/mcp-numpy
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub0
Forks (GitHub) (differs)No figure on GitHub0
Last releaseNot publishedNot published
Where it runs (differs)On your machine (@brain-bbqs/neuro-mcp)On your machine (mcp-numpy)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/brain-bbqs/neuromcpgithub.com/daedalus/mcp-numpy
Changes in the last 7 days00
First seen2026-10-112026-10-11

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

io.github.brain-bbqs/neuro

In its own words, on Official MCP Registry:

Neuroscience MCP server (Python)

io.github.daedalus/mcp-numpy

In its own words, on Official MCP Registry:

An MCP server that exposes NumPy functionality

How to run each

io.github.brain-bbqs/neuro As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio neuro -- npx -y @brain-bbqs/neuro-mcp

io.github.daedalus/mcp-numpy As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio mcp-numpy -- uvx mcp-numpy

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

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: io.github.brain-bbqs/neuro · What it can do: io.github.daedalus/mcp-numpy · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. 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