Ext Ops Panel
Open dashboard
Comparison

helius vs HEY Research Lab

helius is a plugin bundle for AI coding tools published by helius-labs. Marketplaces we read that list it: 2 (Claude Code: claude-plugins-community, Community GitHub marketplaces). HEY Research Lab is an MCP server published by hey-research-lab. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-10-27. 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
MarketplaceheliusHEY Research Lab
Claude Code: claude-plugins-community Listed
Version: 1.1.0
Forks (GitHub): 12
Stars (GitHub): 29
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.3.0
Downloads/month (npm): 1 168
Downloads/week (npm): 395
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
npm registry (MCP servers) Not listed Listed
Version: 0.3.2
Downloads/month (npm): 1 168
Downloads/week (npm): 395
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

helius vs HEY Research Lab
FactheliusHEY Research Lab
Marketplaces that list it22
Stars (GitHub) (differs)29 (better)0 (worse)
Forks (GitHub) (differs)12 (better)0 (worse)
Last release (differs)Not published2026-10-16
Where it runsRemote server or your machineRemote server or your machine
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published2, secrets among them: 1
Parts of the bundle (differs)8Not a bundle
LicenceMITMIT
Repository (differs)github.com/helius-labs/core-aigithub.com/hey-research-lab/hey-research-open
Changes in the last 7 days (differs)21
First seen2026-10-112026-10-11
Endpoint at the last checkResponded 6 days agoResponded 6 days ago

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

helius

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

Build on Solana with Helius — live blockchain tools, expert coding patterns, and autonomous account signup

HEY Research Lab

In its own words, on Official MCP Registry:

Evidence-backed Robinhood Chain research: builders, ships, contracts, changes, market context.

How to run each

helius As a Claude Code plugin

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

HEY Research Lab As a remote MCP server

Claude Code
claude mcp add --transport http hey-research https://heyresearch.xyz/mcp

Requires: HEY_API_KEY (secret)

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

Both endpoints responded at the last daily check. How we check endpoints

Tools each declares

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

Settings each asks for

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

What it can do: helius · What it can do: HEY Research Lab · 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 public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.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