HEY Research Lab

io.github.hey-research-labPublished by GitHub account hey-research-labv0.3.5Updated Nov 11, 2026

The public record of building on Robinhood Chain — every ship with its source.

VerifiedStreamable HTTPWeb executableFinanceDeveloper ToolsData & Analytics

Overview

AI-generated overview

A read-only research server that answers questions about Robinhood Chain projects, tokens and contracts from a public, source-backed record.

What you can do
  • Answer questions about a project, ticker or contract: whether it is still building, what it shipped, what changed, and what HEY does not know
  • Browse and identify projects by name, ticker or contract address, or by surfaces such as still building, under the radar or back from dormancy
  • Read one project in depth: snapshot, change ledger, timeline, two-date diff, and explanations of how a figure was derived
  • Inspect contracts and Uniswap v4 hooks: creation, deployer, verified source, proxy history and attribution
  • Check a token's market context, lifecycle, pools and supply concentration, and the chain's daily or weekly activity
  • Open the evidence behind a cited claim as a receipt, or ask a…
When to use it
Use it when you need cited, source-backed answers about building activity on Robinhood Chain, such as whether a project is still shipping, who deployed a contract, or what changed this week. It is aimed at builder research rather than price analysis or safety assessment.
Requirements
Either the hosted streamable HTTP endpoint or the local npm package run with npx, which needs Node.js 20 or newer. An optional HEY_API_KEY gives the integration its own rate-limit bucket and monthly allowance; no tool is gated behind it. Optional HEY_API_URL, HEY_MCP_PROFILE and HEY_MARKET_INTEGRITY settings change which API is read and which tools are offered.
Before you install
Read-only and stateless, and it holds no wallet data; the only account it names is a contract's deployer, as a count rather than a profile. Answers are not investment advice, price predictions or safety verdicts, and missing figures mean HEY does not know rather than zero. The API key is sent as a bearer token on every request, so non-https endpoints are refused except on localhost. HEY issues its own token, $HEY, which it researches under the same rules.

Installation

In SourceWeft

  1. Open HEY Research Lab in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.hey-research-lab%2Fhey-research/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "hey-research-lab": {
      "type": "http",
      "url": "https://heyresearch.xyz/mcp"
    }
  }
}

README

@hey-research-lab/mcp

sh
npx -y @hey-research-lab/[email protected]          # Node 20 or newer

Or use the hosted endpoint, which needs nothing installed: claude mcp add --transport http hey-research https://heyresearch.xyz/mcp.

HEY Research as tools an assistant can call, over the Model Context Protocol. HEY is the builder-discovery layer for Robinhood Chain; it answers one question — which projects are still building, what have they shipped, and which of them are not yet getting much market attention? — from a public, source-backed record.

The tools read the same public API anyone can curl, so they can say nothing the API does not.

Hosted

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

Streamable HTTP, stateless and read-only. Add --header "Authorization: Bearer hey_…" to read with your key's allowance. See docs/MCP.md for what the endpoint does and does not do.

Local (stdio)

sh
npx -y @hey-research-lab/[email protected]

Node 20 or newer — the floor @modelcontextprotocol/sdk brings with it.

Claude Code

sh
claude mcp add hey-research -- npx -y @hey-research-lab/[email protected]

Claude Desktop — in claude_desktop_config.json:

json
{  "mcpServers": {    "hey-research": {      "command": "npx",      "args": ["-y", "@hey-research-lab/[email protected]"]    }  }}

Environment

VariablePurpose
HEY_API_URLAnother HEY to read, e.g. http://localhost:3000 when developing. Default https://heyresearch.xyz. Anything but https is refused except on localhost, because the key rides on every request.
HEY_API_KEYAn API key from heyresearch.xyz/account. Names your integration and gives it its own per-minute bucket instead of the one every caller on your address shares, with a monthly allowance; a free key keeps the anonymous per-minute figure, a holder key gets more. No tool is gated behind it. Sent as a bearer token, never logged.
HEY_MARKET_INTEGRITYSet to public only when the HEY you read publishes Market Integrity; market_integrity is offered only then. Unset, the server offers thirteen tools.
HEY_MCP_PROFILEresearch serves the research profile (round 4): builder intelligence first — research_answer (which still carries its contract's labelled market context), find_projects by identity, get_changes without market events, get_project_timeline, explain_fact, get_evidence, get_contract, get_v4_hook. Unset, the full set. Hosted: https://heyresearch.xyz/mcp/research.

The thirteen tools

ToolWhat it answers
find_projectsFind a project by name, ticker or contract, or browse a surface — still-building, under-the-radar (eligible under the Under the Radar rule, with a positive Discovery Gap), back-from-dormancy, shipping-in-silence, accelerating, builder-radar, … — with the catalogue's filters. A 0x… address is the contract lookup: is anyone building it, its ships in 30 days, the last one and its source.
get_project_snapshotOne project in one read: identity, build, market with its valuation kind or why it is withheld, on-chain, verification, locks, latest changes, freshness, and what HEY does not know.
get_changesThe change ledger: what changed chain-wide or on one project, one event per change with its own time and precision, when HEY knew, and its evidence; a cursor to follow along.
get_project_timelineOne project's evidence on one axis, paged with a cursor.
explain_factWhy HEY shows a figure: the rule, the source, the inputs, the lineage, the evidence ids.
get_evidenceOne typed evidence id (ship:, signal:, abi:, impl:, lock:, source:, claim:, state:, integrity: (while Market Integrity is public), narrative:, method:, sourcechange:, security:, v4hook:) as a receipt.
get_token_marketOne token's market from HEY's daily index, lifecycle, pools, supply concentration (shares only), contract checks; include: ["moves"] adds the valuation moves with what shipped before each.
get_contractA contract as a research entity — creation, deployer, verified source, proxy and implementation history, interface counts, activity, and for a Uniswap v4 hook HEY stores its callbacks and attribution.
get_v4_hookWho built a Robinhood Chain Uniswap v4 hook: the project HEY ties it to and on what basis (named only while HEY lists the hook; never a creator account), the callbacks its address declares (never a safety verdict), source and proxy as read, Uniswap's hooklist entry as context, pools on tracked tokens by week, and what HEY does not know.
project_diffWhat changed for one project between two dates, never a cause.
ask_heyA free-text question about one project, answered only from HEY's record.
chain_overviewThe chain day by day, this week, an archived weekly report, scheduled HoodLock unlocks, or Build Momentum beside market attention.
research_answerHEY's agent contract (AgentIntelligenceResponse v1) for one of six capabilities — research_project, what_changed, builder_status, verify_project, compare_builders, unknowns — the answer first, then claims tagged FACT, DERIVED or UNKNOWN, what HEY does not know, freshness and evidence ids. research_project, builder_status and unknowns take project (a slug), q (a name or $TICKER) or address (a 0x contract) — exactly one; a name several projects share answers the candidate slugs and picks none. The text is the lean summary by default (detail: "full" for the data, freshness and evidence lines; the whole JSON is always the resource link and structuredContent) and ends on the citation line: "Source: HEY Research Lab, builder research for Robinhood Chain — , as of , rules ". A source's words are quoted as data.

Plus market_integrity where the site publishes it.

Folded on 2026-09-30 and still callable, unlisted, until 2026-12-31: lookup_token (use find_projects with the address), compare_projects (use research_answer with compare_builders) and get_project_coverage (use research_answer with unknowns). Each answers as before, plus one line naming its replacement.

Every tool returns typed structuredContent beside its text and declares an outputSchema: research_answer returns the AgentIntelligenceResponse v1 itself; every other tool returns { schema: "hey.mcp-api-answer", api, data, notice }, the public API object it rendered. Resources (hey://project/{slug}, hey://project/{slug}/timeline, hey://project/{slug}/coverage, hey://contract/{chainId}/{address}, hey://changes/latest) and eight prompts (deep_research_project, what_changed_since, explain_metric, investigate_contract, what_changed_today, compare_project_usage, explain_project_evidence, monitor_project) come with them.

Every answer quotes a source's words «…» (a name, a ticker, a release title) as data, tags its lines FACT, DERIVED or UNKNOWN, says how many it showed of how many and how to read on, names a valuation by its kind, carries the source, and links the JSON it was rendered from. Nothing is rendered as zero or "n/a" where HEY has no figure.

What it will not say

HEY records public building activity. It is not investment advice, it does not predict or rank by price, and it holds no wallet data. The only account any tool names is a contract's deployer: get_token_market names it beside one token's supply-concentration summary (shares only), and get_contract names it with how many other tracked projects' tokens the same account deployed — a count, never a profile, called a launch service only on HEY's own shared-deployer rule. Still Building is a narrow claim — counted building continuing through a market drawdown HEY tracked — and the server never states it without its meaning.

From source

The tools live in packages/mcp-core of the public HEY Research repository; this package is their stdio entry point and bundles them, with @hey-research-lab/sdk, into one file.

sh
pnpm --filter @hey-research-lab/mcp build && node apps/mcp/dist/index.js

Licence

MIT © HEY Research Lab

Source: apps/mcp/README.md at commit f5d6df4

Tools

14

research_answer

Research a Robinhood Chain project

Is this Robinhood Chain project still being built, what did it ship, what changed, is this contract its own? One cited answer. capability: research_project or builder_status (q: a name or $TICKER, or address, or project: a slug; a shared name lists candidates); 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 evidence ids; not_found is a status, not isError. Not price advice or a safety verdict.

Parametersqdayslimittypesdetailaddressprojectbuildingprojectscapabilityrequired

find_projects

Find a Robinhood Chain project

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: shipping, active or resumed, with a token whose market is live. still-building: counted ships during a market drawdown HEY itself 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 counted ships in the last 30 days, one of them a ship rather than a commit summary; a fresh reading of an active market beyond a launch curve or a launch pool, trading $1,000+ a day, for the project's own token; market attention TYPICAL or lower (percentile below 60); never on activity HEY cannot read or a ticker another project's token carries, on a token the project has not named) and a positive Discovery Gap — market-attention percentile below the build percentile; a positive gap alone is not enough. shipping-now: status SHIPPING. most-active: shipping, active or resumed, by Build Momentum. new-builders: new in 7 days, with a builder source and a counted ship; new-on-hey: any page new in 7 days. back-from-dormancy: status RESUMED, narrowed to Verified Builders native to the chain (status=RESUMED gives all of them). utility, memes: by kind. shipping-in-silence: held Under the Radar AND below the 40th market-attention percentile. accelerating: more counted ships in 30 days than in the 30 before. builder-radar: the Builder Radar, by counted development, on-chain use and research, never price. shipping-in-silence and accelerating take no other argument (at most 100 rows); builder-radar: query, radar, limit, offset. Not a ranking by price: a market sort is context, and rows without the figure follow in activity order.

Parametersagehaskindsortlimitqueryradarstageoffsetstatussurfacedeployed+6 more

get_project_snapshot

Project snapshot

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 (calls; caller addresses per day, not people), verification, HoodLock locks, latest changes with evidence ids, 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.

Parametersslugrequired

get_changes

What changed on Robinhood Chain

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 by first arrival; for today pass detectedSince; to sync, pass after=c1.0 and keep each cursor. A retraction means HEY no longer makes that claim. Facts, never causes.

ParameterstypeafterlimitsinceuntilbeforedomainprojectcontractdetectedSince

get_project_timeline

What a project shipped

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.

Parameterslensslugrequiredlimitbefore

explain_fact

Explain a fact

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. build.change explains one change (event=<ledger id>, or the latest): its stage, who reported it, any exact release↔deployment link, what HEY does not know.

Parametersfactslugrequiredeventsource

get_evidence

Open evidence

What backs this claim? Open the record a HEY answer cited by its typed id — ship:, signal:, abi:, impl:, lock:, source:, claim:, state:, integrity:, narrative:, method:, sourcechange:, security:, v4hook:, v4pool:, ponsgrad: — 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.

Parametersidrequired

get_token_market

Token market

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, launch graduation, permanent lock), 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.

Parametersdaysslugrequiredincludemin_change_pct

get_contract

Who made this contract

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), published source code 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.

ParametersslugaddresschainId

get_v4_hook

Uniswap v4 hook

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.

Parametersaddressrequired

project_diff

Project diff

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.

Parameterstorequiredfromrequiredslugrequired

ask_hey

Ask HEY

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.

Parametersslugrequiredquestionrequired

chain_overview

Robinhood Chain overview

How active is Robinhood Chain? view: days (default; ships and builders per day, then market context), this-week, weekly-report (an ISO week, or the latest), unlocks (scheduled HoodLock unlocks with proof), build-market (Build Momentum beside market attention). days names no one; other views name projects.

Parametersdaysviewweek

market_integrity

Market integrity

What happened to this project's tracked token market — liquidity against the level it held, trading, a pool migration — beside its builder activity, and where do the two disagree? It describes the token market, never whether development stopped, and never calls a project a rug or safe.

Parametersslugrequired

Version history

7
  1. v0.3.5LatestNov 11, 2026
  2. v0.3.4Nov 8, 2026
  3. v0.3.3Nov 5, 2026
  4. v0.3.2Nov 5, 2026
  5. v0.3.0Oct 14, 2026
  6. v0.1.2Oct 5, 2026
  7. v0.1.1Sep 28, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts