HEY Research Lab
MCP serverDev toolsLets your agent pull evidence-backed Robinhood Chain research covering builders, contract updates, and market context.
Available today. Use it from your connected AI after setup.
No other account needed.
Add ahel to your AI once: Claude, ChatGPT, Cursor, Claude Code or Codex. Then ask it to use this.
Then ask your AI: use HEY Research Lab to find projects
About this server
Evidence-backed Robinhood Chain research: builders, ships, contracts, changes, market context.
Install HEY Research Lab
The server’s own address, for the clients that take one directly. Or connect ahel onceand every client you use reads it from one address, with the account kept on ahel rather than in each client’s config.
Claude Code
claude mcp add --transport http --scope user hey-research-lab 'https://heyresearch.xyz/mcp'Run it once in your project, then open /mcp to approve any sign-in the server asks for.
Claude Desktop
https://heyresearch.xyz/mcpAdd a custom connector in Settings, paste this address, and approve the sign-in.
Cursor
cursor://anysphere.cursor-deeplink/mcp/install?name=hey-research-lab&config=eyJ1cmwiOiJodHRwczovL2hleXJlc2VhcmNoLnh5ei9tY3AifQ==Open the link and Cursor adds the server at that address.
ChatGPT
https://heyresearch.xyz/mcpIn Settings, enable Developer mode, create an MCP app, and paste this address. Your plan and workspace must allow custom apps.
Codex
codex mcp add hey-research-lab --url 'https://heyresearch.xyz/mcp'Run it once, then sign in with codex mcp login hey-research-lab if the server asks for an account.
From the project's README
As published by hey-research-lab/hey-research-open in README.md.
Find who's actually building on Robinhood Chain.
Site · Public API · MCP server · Sources · Changelog
The question
Not which wallet bought and not which token is pumping, but:
Which projects are still building, what have they shipped, and which of them is nobody looking at?
Every answer on HEY is a fact with the source it came from. There is no score of a project's worth, no grade, no verdict, and the words rug and scam appear nowhere in the product — an end-to-end test asserts it.
What it looks like
| Explore the catalogue | One project's evidence |
|---|---|
| Builder Radar | HEY Signal |
|---|---|
| Pulse — the chain, day by day | Ships — what landed |
|---|---|
| Scout — earn by finding evidence | Bounties — set in dollars, paid in HEY |
|---|---|
| Developers | Methodology — every rule, stated |
|---|---|
| Home, 375px | A project, 375px |
|---|---|
Captured from production on 20 September 2026.
In this repository
This is the published half of HEY: the parts that stand on their own and are safe to read.
| Path | What it is |
|---|---|
packages/sources | Every public-data adapter HEY reads — GitHub, Blockscout, Sourcify (verification and its signature database), DEX Screener, GeckoTerminal, CoinGecko, launchpads, feeds, npm, deps.dev, OSV — each with saved fixtures and contract tests. The tests fail on a real network call. All of them go through one fetch guard (private-address and DNS-rebinding checks, redirect and credential rules, size, time and content-type limits) and bounded HTML and XML parsers, tested against hostile pages and feeds. |
packages/scoring | Activity status, Build Momentum, Still Building and Under the Radar, deterministic and versioned. They read no price and no balance, and that is tested. |
packages/sdk | @hey-research-lab/sdk, the typed client over the public API. No dependencies, ESM and CJS, Node 18 or a browser. |
packages/mcp-core | The MCP tools, renderers, resources and prompts with no transport: fourteen read-only tools, each answer tagged FACT, DERIVED or UNKNOWN. |
apps/mcp | @hey-research-lab/mcp, the stdio entry point that bundles them. Node 20. The same tools are hosted at https://heyresearch.xyz/mcp. |
packages/config | Environment schema and chain constants. |
packages/ui | The presentation components — cards, chips, status, formatting. |
docs/ | The public API, the MCP server, the source registry, and every data source with what it refuses and why. |
The ingestion pipeline, the quality gate, the database schema, the web app and the operations tooling stay in the private repository.
Quickstart
Use the packages from npm (published 27 September 2026):
npm i @hey-research-lab/sdk # the typed client
claude mcp add hey-research -- npx -y @hey-research-lab/mcp # the MCP server
Or build this tree:
pnpm install
pnpm lint && pnpm typecheck && pnpm test # 686 tests, no network
pnpm --filter @hey-research-lab/sdk build # packages/sdk/dist
pnpm --filter @hey-research-lab/mcp build # apps/mcp/dist/index.js
Use the API
No key needed for the read API. 120 requests a minute anonymously, more with a key.
One address, one line — the call a trading bot makes:
curl "https://heyresearch.xyz/api/v1/scan?chain=4663&token=0xB33eb16782776b4D738c0Fd643577cb0284Db610"
{
"found": true,
"status": "shipping",
"status_label": "Shipping",
"verified_builder": true,
"activity": { "commits_30d": 100, "releases_30d": 1, "ships_30d": 3, "last_ship": "2026-09-18" },
"project_url": "https://heyresearch.xyz/project/hey-research-lab",
"cta": { "label": "See the builder on HEY", "url": "…" }
}
A token HEY has no published page for answers 200 with found: false, so a bot prints nothing
rather than guessing.
The same thing, typed:
import { HeyClient, HeyApiError } from '@hey-research-lab/sdk';
const hey = new HeyClient();
const card = await hey.scanCard(4663, address);
if (!card.found) return null;
for await (const project of hey.projects.items({ tab: 'still-building' })) {
console.log(project.slug, project.lastShippedAt ?? 'no ship recorded');
}
A listed project with a token carries tokenMarket — the market state the card shows — and the
single-project route sends everything the listing does. /api/projects/{slug}/market adds the
contract's deployer, its pools and 1% depth, and a supply-concentration summary with no addresses
(2026-09-25).
/api/projects/{slug}/relationships lists what a project is connected to and why HEY thinks so —
every edge with its standing and evidence, never an account and never a "partnership" — and the
snapshot's peerContext places some of its figures among comparable projects, one figure at a time,
never as a combined score (2026-09-28).
Paging follows the API's own cursor, a 429 arrives as HeyApiError with retryAfterSeconds
and is never retried for you, and an absent field means HEY does not know — never a zero.
For an assistant — fourteen read-only tools over the same API, hosted or on your machine:
claude mcp add --transport http hey-research https://heyresearch.xyz/mcp
# or locally
pnpm --filter @hey-research-lab/mcp build
claude mcp add hey-research -- node "$PWD/apps/mcp/dist/index.js"
Full reference: docs/PUBLIC_API.md · docs/MCP.md · docs/INTEGRATIONS.md — the line to render, the three answers to handle, and the four things not to do.
For autonomous agents
From the domain alone, with no JavaScript and no cookies:
| Entry point | What it is |
|---|---|
https://heyresearch.xyz/llms.txt | What HEY is, what it will not do, every machine entry point (llms.txt v2) |
https://heyresearch.xyz/.well-known/agent-card.json | A2A 1.0 Agent Card; JSON-RPC at /api/a2a, six read-only skills |
https://heyresearch.xyz/openapi.json | OpenAPI 3.1 for the public API |
https://heyresearch.xyz/mcp | Hosted MCP (Streamable HTTP); registry name io.github.hey-research-lab/hey-research (apps/mcp/server.json) |
https://heyresearch.xyz/api/hey/profile | $HEY as research data: each utility LIVE, PLANNED, RETIRED or UNKNOWN |
https://heyresearch.xyz/developers/agents | The guide (Markdown at /developers/agents.md) |
An agent that forms a thesis can record it as an AgentResearchReceipt — neutral, for any project, checked but never stored or endorsed by HEY. HEY gives no trade instructions and runs no agents of its own.
The badge
Any project HEY tracks can embed its own status. It updates itself, and it links back to the evidence behind it.
[](https://heyresearch.xyz/project/<slug>)
?theme=dark and ?style=pill are the other two looks. docs/BADGES.md on the site.
Rules that do not move
- Building is not price. Market cap, liquidity and volume are context and filters. Nothing in
packages/scoringreads a price or a balance; a neutrality test fails the build if it ever does. - Paying changes nothing organic. Bounties, sponsorships, claims and
$HEYholdings never move a rank, a status or a score. - No wallet analytics. No PnL, no smart-money or whale labels, no wallet profiles, no clustering presented as a claim about people, no copy-trading. The schema guard fails the build on the words. One exception, decided on 2026-09-14: a bubble map of a single token's largest balances on that token's market page. An address there is a point on a chart of one supply — never a person, never scored, never ranked across tokens, never an input to any status or score.
- Absent means unknown. A figure HEY has not measured is omitted, never published as zero.
- Security is evidence, never a verdict. An audit shows an audit took place; it is not a guarantee of safety. HEY says where a report is published and where it found the link — no score, no "safe", and "no advisory found" is a reading of one index, never a clean bill.
- A model is never the source of truth. AI-assisted interpretation is optional and off by
default; when on, it reads only HEY's own evidence, cites it by id, is labelled as an
interpretation, and never moves a status, a score or a rank.
AI_PROVIDERacceptsdisabledoranthropiconly. - Every claim carries its source. And none of them is a buy signal.
The full rules, with the thresholds they use, are on the methodology page.
$HEY, briefly
$HEY (0xB33eb16782776b4D738c0Fd643577cb0284Db610 on Robinhood Chain) pays for evidence:
research bounties set in dollars and paid in HEY, claim bonds, and priority on research requests.
Holding changes what a reader pays, when they see new research and how much API the lab serves
them. It never buys a rank, a status or a score.
How this repository is produced
A script in the private repository copies the paths listed above, generates a types-only
@hey/db, refuses to publish anything that must not leave, and pushes one commit per sync. Issues
and pull requests are welcome here: a change accepted here is applied privately and comes back in
the next sync.
HEY reports what teams ship and whether a tracked token still has a market. It does not predict prices, and nothing in it is investment advice.
MIT licence. See CHANGELOG.md for what has changed and when.
Tools it offers (15)
What this server listed when ahel dialed its public endpoint in Sep 2026, with no key and no account of yours. The names are the server’s own.
find_projectslookup_tokenget_project_snapshotget_changesget_project_timelineget_project_coverageexplain_factget_evidenceget_token_marketget_contractproject_diffcompare_projectsask_heychain_overviewmarket_integrity
Signals
- Last commit
- Sep 2026
Advanced
- Delivery
- hey-research MCP server → your ahel connector (mcp.ahel.ai) → your AI.
- Item type
- mcp-server
- Key
io-github-hey-research-lab-hey-research- Source
- github.com/hey-research-lab/hey-research-open
- Hosted endpoint
https://heyresearch.xyz/mcp