HEY Research Lab
NPM · @HEY-RESEARCH-LAB/MCP · 3 COMPONENTS
Evidence-backed Robinhood Chain research: builders, ships, contracts, changes, market context.
Available components
Last scanned (5 hours ago)
Scores higher than 39% of npm servers
Category Crypto and Web3
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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- 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
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 7 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability72
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 3243 tokens (~231/item across 14 items; 13 tools + 1 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 Management33
- Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage89
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 62% of tool parameters carry a description.Partial
- 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
- We read all 13 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 21 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.
- 19 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 26 +31
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Stability: unverified → 0.03 ▲ functional
- First check of Schema quality: fail functional
- First check of Tool coverage: 62 functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: fail functional
- First check of Schema quality: good functional
- First check of Tool coverage: 100 functional
- 14 Oct 26 0
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- MCP protocol: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- First check of Tool coverage: 100 functional
- First check of Schema quality: fail functional
- First check of Schema quality: excellent functional
- First check of Tool coverage: 65 functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: fail functional
- Package version: 0.1.2 → 0.3.0 functional
- 13 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
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 npm/@hey-research-lab/mcp@0.3.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
ask_hey Ask HEY ~98
Asking something else about one project? Put it in free text, by slug, in English or Malay ("did they ship this month?"). HEY answers only from its record, every line tagged FACT, DERIVED or UNKNOWN with its source. Building only; no view on price.
| Name | Type | Req | Description |
|---|---|---|---|
| question | string | yes | The question, in the reader's words. |
| slug | string | yes | A project slug, e.g. "agentos". |
| Name | Type | Req | Description |
|---|---|---|---|
| api | string | yes | – |
| data | – | – | – |
| schema | string | yes | – |
No examples provided.
chain_overview Robinhood Chain overview ~136
How active is Robinhood Chain as a whole? view: days (default; trades, volume, tokens, transactions, launches, ships per day), this-week, weekly-report (an ISO week, or the latest), unlocks (scheduled HoodLock unlocks with proof), build-market (Build Momentum beside market attention). Aggregates only; nobody is named.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | days: 1–400 (default 14); unlocks: 1–365 ahead (default 30). |
| view | string | – | – |
| week | string | – | weekly-report: e.g. 2026-W37. |
| Name | Type | Req | Description |
|---|---|---|---|
| api | string | yes | – |
| data | – | – | – |
| schema | string | yes | – |
No examples provided.
explain_fact Explain a fact ~117
Why does HEY say a project is Shipping, Dormant or Still Building, or show a figure? The value, FACT, DERIVED or UNKNOWN, the rule and version, the winning source, the inputs, the lineage and the evidence ids. Omit fact to list what can be explained; source.counted takes a source id.
| Name | Type | Req | Description |
|---|---|---|---|
| fact | string | – | – |
| slug | string | yes | A project slug, e.g. "agentos". |
| source | string | – | With fact=source.counted: the source id. |
| Name | Type | Req | Description |
|---|---|---|---|
| api | string | yes | – |
| data | – | – | – |
| schema | string | yes | – |
No examples provided.
find_projects Find a Robinhood Chain project ~662
Which Robinhood Chain project is this name, $TICKER or 0x contract, and is anyone building it? A full 0x address is a contract lookup: its ships in 30 days, the last one with its source. Or browse who is shipping now, back from dormancy, accelerating or building ahead of market attention. Surfaces: building-with-token: verified shipping, active or resumed, with a token whose market is live. still-building: verified activity continuing through a market drawdown HEY tracked. under-the-radar: eligible under HEY's Under the Radar rule (status shipping, active or resumed; Build Momentum at least 30; at least 2 meaningful events in the last 30 days, one of them a ship rather than a commit summary; a fresh reading of an active market, not a thin one or only a launch curve, for the project's own token) and a positive Discovery Gap — market-attention percentile below the build percentile; a positive gap alone is not enough, and it does not bound attention itself. shipping-now: status SHIPPING. most-active: shipping, active or resumed, by Build Momentum. new-builders: recorded in the last 7 days. back-from-dormancy: status RESUMED, narrowed to verified builders native to the chain (status=RESUMED gives every resumed project). utility, memes: by kind. shipping-in-silence: eligible under the Under the Radar rule AND below the 40th market-attention percentile. accelerating: more meaningful events in 30 days than in the 30 before. builder-radar: the Builder Radar, ranked by verified development, on-chain use and research, never price. shipping-in-silence and accelerating take no other argument (at most 100 rows); builder-radar takes query, radar, limit and offset. Not a ranking by price: a market sort is context, and rows without the figure follow in activity order.
| Name | Type | Req | Description |
|---|---|---|---|
| age | string | – | Since the first pool opened. |
| deployed | string | – | Since the contract was deployed. |
| has | array | – | Facts every row must carry. |
| kind | string | – | – |
| launchpad | string | – | e.g. "pons", "virtuals". |
| limit | integer | – | Default 24. |
| maxMarketCap | number | – | USD, on the card's valuation reading. |
| minLiquidity | number | – | USD; unknown is excluded, never zero. |
| minMarketCap | number | – | – |
| minVolume | number | – | 24h volume, USD. |
| narrative | string | – | Narrative slug, e.g. "ai-agents". |
| offset | integer | – | The offset a previous answer gave. |
| query | string | – | Name, $TICKER or 0x contract (or its start). |
| radar | string | – | With surface=builder-radar: a Radar view. |
| sort | string | – | Default activity; shipped = newest ship first; shipped7d / shipped30d = most meaningful ships in the last 7 / 30 days. |
| stage | string | – | Token launch stage. |
| status | string | – | Activity status. |
| surface | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| api | string | yes | – |
| data | – | – | – |
| schema | string | yes | – |
No examples provided.
get_changes What changed on Robinhood Chain ~251
What changed on Robinhood Chain today or this week, or for one project or contract? The change ledger: releases, ships, status moves, contract deploys and upgrades, verification, sources, unlocks — one event per change with its own time and precision, when HEY first knew, and its evidence. Newest first; for today pass detectedSince; to follow, pass after=c1.0 and keep each cursor. A retraction means HEY no longer makes that claim. Facts, never causes.
| Name | Type | Req | Description |
|---|---|---|---|
| after | string | – | Sync forward from this cursor (c1.0 is the start). |
| before | string | – | Browse older than this cursor. |
| contract | string | – | <chainId>:<address>. |
| detectedSince | string | – | ISO instant: start a sync at the first event HEY recorded at or after it. |
| domain | array | – | – |
| limit | integer | – | Default 30. |
| project | string | – | A project slug. |
| since | string | – | ISO date: events whose own time is at or after it (events with no source time are left out). |
| type | array | – | – |
| until | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| api | string | yes | – |
| data | – | – | – |
| schema | string | yes | – |
No examples provided.
get_contract Who made this contract ~175
Who made this Robinhood Chain contract, and is it a known project's? Project, creation, deployer (the only account named, with a count of other tracked projects' tokens it deployed), verified source and whose code it is (template, bytecode match or its own), Sourcify's answer, proxy and implementation history, interface changes, 7 days of calls per method (counts, names withheld; a selector's signature candidate — a guess, never a name). Address (chainId default 4663) or slug for all of a project's. An unread proxy is "not read", never "not a proxy". Not a safety verdict.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | – |
| chainId | integer | – | Default 4663. |
| slug | string | – | A project slug, for all of its contracts. |
| Name | Type | Req | Description |
|---|---|---|---|
| api | string | yes | – |
| data | – | – | – |
| schema | string | yes | – |
No examples provided.
get_evidence Open evidence ~117
What backs this claim? Open the record a HEY answer cited by its typed id — ship:, signal:, abi:, impl:, lock:, source:, claim:, state:, narrative:, method:, sourcechange:, security:, v4hook: — as a receipt: what it claims, its source URL, when it happened at what precision, when HEY knew, how it is backed. A withdrawn record says so.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | A typed evidence id, e.g. "ship:2ac87a66-…". |
| Name | Type | Req | Description |
|---|---|---|---|
| api | string | yes | – |
| data | – | – | – |
| schema | string | yes | – |
No examples provided.
get_project_snapshot Project snapshot ~135
Where does this Robinhood Chain project stand? One read by slug — the Research Summary, identity, activity status and Build Momentum, last ships, market context with its kind or why it is withheld, on-chain use, 7-day usage (distinct caller addresses, not people), verification, HoodLock locks, latest changes, freshness and what HEY does not know. Context blocks, never building: paid promotion (presence and dates), DefiLlama protocol economics (measured, not tracked or unread), developer footprint. Not price advice.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | A project slug, e.g. "agentos". |
| Name | Type | Req | Description |
|---|---|---|---|
| api | string | yes | – |
| data | – | – | – |
| schema | string | yes | – |
No examples provided.
get_project_timeline What a project shipped ~122
What did this project ship, and when? Builds, releases, code, contract deploys, upgrades and interface changes, token verification, locks and unlocks, each with how precisely HEY knows its time. Lenses: everything, build, code, onchain, market, locks. Paged with the before cursor.
| Name | Type | Req | Description |
|---|---|---|---|
| before | string | – | The cursor the previous answer gave. |
| lens | string | – | – |
| limit | integer | – | Default 30. |
| slug | string | yes | A project slug, e.g. "agentos". |
| Name | Type | Req | Description |
|---|---|---|---|
| api | string | yes | – |
| data | – | – | – |
| schema | string | yes | – |
No examples provided.
get_token_market Token market ~162
Does this token still trade? Context beside the building, from HEY's daily index: current reading (valuation kind, provider), price, liquidity, volume and trades by day, lifecycle (deploy, launchpad claim, stage, first trade), pools and depth, supply concentration (shares only, no addresses), contract checks. include=["moves"] adds each day-on-day valuation move with the building events published before it — a sequence, never a cause. Not price advice.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Days of history; default 30. |
| include | array | – | – |
| min_change_pct | integer | – | With moves: smallest move in percent; default 25. |
| slug | string | yes | A project slug, e.g. "agentos". |
| Name | Type | Req | Description |
|---|---|---|---|
| api | string | yes | – |
| data | – | – | – |
| schema | string | yes | – |
No examples provided.
get_v4_hook Uniswap v4 hook ~70
Who built this Robinhood Chain Uniswap v4 hook? The project HEY ties it to and why (named only while listed; never a creator account), declared callbacks (not a safety verdict), source, hooklist entry, pools by week and unknowns.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| api | string | yes | – |
| data | – | – | – |
| schema | string | yes | – |
No examples provided.
project_diff Project diff ~97
What changed for this project between two dates (YYYY-MM-DD, at most 400 days apart)? Releases and meaningful ships, status, Build Momentum, valuation and liquidity then and now, and the changes recorded — each from the nearest persisted point with its date and basis. Never a cause.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | yes | – |
| slug | string | yes | A project slug, e.g. "agentos". |
| to | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| api | string | yes | – |
| data | – | – | – |
| schema | string | yes | – |
No examples provided.
research_answer Research a Robinhood Chain project ~203
Is this Robinhood Chain project still being built, what did it ship, what changed, is this contract its own? One bounded answer, cited. capability: research_project or builder_status (q: a name or $TICKER, or address, or project: a slug; a name several projects share lists them); what_changed (project or chain, 1–30 days); verify_project (address, project?); compare_builders (2–4, no winner); unknowns (every coverage state). Claims FACT/DERIVED/UNKNOWN with freshness and evidence ids. Not price advice or a safety verdict.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | – |
| building | string | – | – |
| capability | string | yes | – |
| days | integer | – | – |
| detail | string | – | – |
| limit | integer | – | – |
| project | string | – | – |
| projects | array | – | – |
| q | string | – | – |
| types | array | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| answer | object | yes | – |
| capability | string | yes | – |
| claims | array | yes | – |
| data | – | yes | – |
| evidence | array | yes | – |
| schema | string | yes | – |
| schemaVersion | string | yes | – |
| status | string | yes | – |
No examples provided.
How do I install the HEY Research Lab MCP server?
HEY Research Lab runs locally as an npm package, launched with npx -y @hey-research-lab/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @hey-research-lab/mcp
claude mcp add hey-research-lab-hey-research -- npx -y @hey-research-lab/mcp
What is the HEY Research Lab MCP server?
HEY Research Lab is an MCP server listed in the public MCP registry as io.github.hey-research-lab/hey-research. Evidence-backed Robinhood Chain research: builders, ships, contracts, changes, market context. This page covers its npm package (@hey-research-lab/mcp).
Is the HEY Research Lab MCP server safe to use?
HEY Research Lab scores 68 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 24 October 2026. It declares no install or post-install scripts. 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 HEY Research Lab MCP server expose?
HEY Research Lab exposes 13 tools: research_answer, find_projects, get_project_snapshot, get_changes, get_project_timeline, and 8 more. Their descriptions and schemas cost roughly 2,345 tokens of context every time the server is loaded.
Is the HEY Research Lab MCP server still maintained?
HEY Research Lab 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.
What licence is the HEY Research Lab MCP server under?
HEY Research Lab declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.