Ext Ops Panel
Open dashboard
Comparison

Needle Remote vs Block Genomics — Nexus Protocol

Needle Remote is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). Block Genomics — Nexus Protocol is an MCP server published by BitmapAsset. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-13. 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
MarketplaceNeedle RemoteBlock Genomics — Nexus Protocol
Docker MCP Catalog Listed
Version: not stated
No figure published
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.2
Downloads/month (npm): 182
Downloads/week (npm): 39
Forks (GitHub): 0
Stars (GitHub): 1
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

Needle Remote vs Block Genomics — Nexus Protocol
FactNeedle RemoteBlock Genomics — Nexus Protocol
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub1
Forks (GitHub) (differs)No figure on GitHub0
Last releaseNot publishedNot published
Where it runs (differs)Remote server (mcp.needle.app/mcp)On your machine (block-genomics-mcp)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 15, secrets among them: 2
Licence (differs)Apache-2.0Not stated
Repository (differs)Not statedgithub.com/bitmapasset/block-genomics-nexus
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)not checked yetno remote endpoint we check

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

Needle Remote

In its own words, on Docker MCP Catalog:

Production-ready RAG service to search and retrieve data from your documents.

Block Genomics — Nexus Protocol

In its own words, on Official MCP Registry:

Prove Bitcoin block ownership via BIP-322 and register sovereign AI agents on the Nexus Protocol.

How to run each

Needle Remote As a remote MCP server

Claude Code
claude mcp add --transport http needle https://mcp.needle.app/mcp

Requires: NEEDLE_API_KEY (secret)

Block Genomics — Nexus Protocol As a local MCP server: npm package

Claude Code
claude mcp add --env "BG_AGENT_TOKEN=<YOUR_BG_AGENT_TOKEN>" --env "BG_API_KEY=<YOUR_BG_API_KEY>" --transport stdio block-genomics-mcp -- npx -y block-genomics-mcp

Requires: BG_AGENT_TOKEN (secret), BG_API_KEY (secret)

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

Only Needle Remote asks for

  • NEEDLE_API_KEY (secret)

Only Block Genomics — Nexus Protocol asks for

  • BG_AGENT_TOKEN (secret)
  • BG_API_BASE
  • BG_API_KEY (secret)
  • BG_ENABLE_WRITES
  • BG_TIMEOUT_MS

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: Needle Remote · What it can do: Block Genomics — Nexus Protocol · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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