# HEY Research Lab (remote · heyresearch.xyz)

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

- Trust score: 81/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-24

## Components

- remote · `heyresearch.xyz`: 81/100 (this document), [markdown](https://verifymcp.io/servers/hey-research-lab-hey-research/heyresearch.md), [page](https://verifymcp.io/servers/hey-research-lab-hey-research/heyresearch)
- remote · `heyresearch.xyz`: 80/100, [markdown](https://verifymcp.io/servers/hey-research-lab-hey-research/mcp-research.md), [page](https://verifymcp.io/servers/hey-research-lab-hey-research/mcp-research)
- npm · `@hey-research-lab/mcp`: 68/100, [markdown](https://verifymcp.io/servers/hey-research-lab-hey-research/hey-research-lab-mcp.md), [page](https://verifymcp.io/servers/hey-research-lab-hey-research/hey-research-lab-mcp)

## Channel facts

- Endpoint: `https://heyresearch.xyz/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.3.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-24.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 72/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 3547 tokens (~236/item across 15 items; 14 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 67/100
  - Stability check failed: schema churn in the 26 days we've observed: 3 tool removals, 0 breaking changes, 0 auth/transport breaks, 2 additions.
- **Tool Coverage**: 89/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 63% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the HEY Research Lab MCP server?

HEY Research Lab is a hosted endpoint at https://heyresearch.xyz/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http hey-research-lab-hey-research 'https://heyresearch.xyz/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "hey-research-lab-hey-research": {
      "url": "https://heyresearch.xyz/mcp"
    }
  }
}
```

### VS Code

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

### Codex

```toml
[mcp_servers.hey-research-lab-hey-research]
url = "https://heyresearch.xyz/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "hey-research-lab-hey-research": {
      "type": "remote",
      "url": "https://heyresearch.xyz/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add hey-research-lab-hey-research --url 'https://heyresearch.xyz/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  hey-research-lab-hey-research:
    url: "https://heyresearch.xyz/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "hey-research-lab-hey-research": {
      "Transport": "http",
      "Url": "https://heyresearch.xyz/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add hey-research-lab-hey-research -t streamable-http -u 'https://heyresearch.xyz/mcp'
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-23 (score 81, +1)

- [security] Tool “research_answer” rewrote its description, which is the text the model reads

### 2026-10-21 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57.

### 2026-10-20 (score 79, 0)

- [security] Tool “explain_fact” rewrote its description, which is the text the model reads
- [security] Tool “find_projects” rewrote its description, which is the text the model reads
- [cosmetic] “explain_fact” added an optional parameter “event”

### 2026-10-18 (score 79, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “research_answer” rewrote its description, which is the text the model reads
- [security] Tool “find_projects” rewrote its description, which is the text the model reads
- [security] Tool “chain_overview” rewrote its description, which is the text the model reads

### 2026-10-17 (score 78, +55)

- [security regression] Stability: unverified → fail
- [security improvement] Authorization: unverified → partial
- [security improvement] Injection markers: unverified → pass
- [security improvement] HSTS header: unverified → pass
- [security improvement] Transport: fail → pass
- [security] Tool “chain_overview” rewrote its description, which is the text the model reads
- [security] Tool “get_token_market” rewrote its description, which is the text the model reads
- [security] Tool “get_project_snapshot” rewrote its description, which is the text the model reads
- [security] Tool “get_evidence” rewrote its description, which is the text the model reads
- [security] Tool “get_changes” rewrote its description, which is the text the model reads
- [security] Tool “find_projects” rewrote its description, which is the text the model reads
- [functional improvement] Endpoint reachability: not serving MCP → reachable
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] Schema quality: unverified → 100
- [functional improvement] MCP protocol: unverified → pass
- [functional] Server version: 0.3.0 → 0.3.2

### 2026-10-16 (score 23, −54)

- [security regression] Endpoint reachability: reachable → not serving MCP
- [security regression] HSTS header: pass → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] Authorization: partial → unverified
- [security regression] Stability: fail → unverified
- [security regression] Transport: pass → fail
- [functional regression] Schema quality: 100 → unverified
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified

### 2026-10-14 (score 77, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “research_answer” rewrote its description, which is the text the model reads
- [functional] Server version: 0.2.0 → 0.3.0
- [cosmetic] “research_answer” added an optional parameter “q”
- [cosmetic] “research_answer” added an optional parameter “detail”

### 2026-10-13 (score 77, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “research_answer” rewrote its description, which is the text the model reads
- [security] Tool “get_project_snapshot” rewrote its description, which is the text the model reads
- [security] Tool “get_project_timeline” rewrote its description, which is the text the model reads
- [security] Tool “ask_hey” rewrote its description, which is the text the model reads
- [security] Tool “chain_overview” rewrote its description, which is the text the model reads
- [security] Tool “explain_fact” rewrote its description, which is the text the model reads
- [security] Tool “find_projects” rewrote its description, which is the text the model reads
- [security] Tool “get_changes” rewrote its description, which is the text the model reads
- [security] Tool “get_contract” rewrote its description, which is the text the model reads
- [security] Tool “get_evidence” rewrote its description, which is the text the model reads
- [security] Tool “get_token_market” rewrote its description, which is the text the model reads
- [security] Tool “get_v4_hook” rewrote its description, which is the text the model reads
- [security] Tool “market_integrity” rewrote its description, which is the text the model reads
- [security] Tool “project_diff” rewrote its description, which is the text the model reads
- [cosmetic] “find_projects” reworded the description of “query”
- [cosmetic] Tool “chain_overview” changed its title: Chain overview → Robinhood Chain overview
- [cosmetic] Tool “find_projects” changed its title: Find projects → Find a Robinhood Chain project
- [cosmetic] Tool “get_changes” changed its title: What changed → What changed on Robinhood Chain
- [cosmetic] Tool “get_contract” changed its title: Contract → Who made this contract
- [cosmetic] Tool “get_project_timeline” changed its title: Project timeline → What a project shipped
- [cosmetic] Tool “research_answer” changed its title: Agent research answer → Research a Robinhood Chain project

## MCP tools (14)

### `research_answer` (~207 tokens)

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.

Input parameters:

- `address` (string)
- `building` (string)
- `capability` (string, required)
- `days` (integer)
- `detail` (string)
- `limit` (integer)
- `project` (string)
- `projects` (array)
- `q` (string)
- `types` (array)

Output parameters:

- `answer` (object)
- `capability` (string)
- `claims` (array)
- `data`
- `evidence` (array)
- `schema` (string)
- `schemaVersion` (string)
- `status` (string)

### `find_projects` (~706 tokens)

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: 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 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 contested unverified ticker) 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 every resumed project). utility, memes: by kind. shipping-in-silence: held Under the Radar 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.

Input parameters:

- `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)

Output parameters:

- `api` (string)
- `data`
- `schema` (string)

### `get_project_snapshot` (~141 tokens)

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.

Input parameters:

- `slug` (string, required): A project slug, e.g. "agentos".

Output parameters:

- `api` (string)
- `data`
- `schema` (string)

### `get_changes` (~254 tokens)

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.

Input parameters:

- `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)

Output parameters:

- `api` (string)
- `data`
- `schema` (string)

### `get_project_timeline` (~122 tokens)

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.

Input parameters:

- `before` (string): The cursor the previous answer gave.
- `lens` (string)
- `limit` (integer): Default 30.
- `slug` (string, required): A project slug, e.g. "agentos".

Output parameters:

- `api` (string)
- `data`
- `schema` (string)

### `explain_fact` (~177 tokens)

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.

Input parameters:

- `event` (string): With fact=build.change: a change-ledger id; omit for the latest.
- `fact` (string)
- `slug` (string, required): A project slug, e.g. "agentos".
- `source` (string): With fact=source.counted: the source id.

Output parameters:

- `api` (string)
- `data`
- `schema` (string)

### `get_evidence` (~127 tokens)

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.

Input parameters:

- `id` (string, required): A typed evidence id, e.g. "ship:2ac87a66-…".

Output parameters:

- `api` (string)
- `data`
- `schema` (string)

### `get_token_market` (~168 tokens)

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.

Input parameters:

- `days` (integer): Days of history; default 30.
- `include` (array)
- `min_change_pct` (integer): With moves: smallest move in percent; default 25.
- `slug` (string, required): A project slug, e.g. "agentos".

Output parameters:

- `api` (string)
- `data`
- `schema` (string)

### `get_contract` (~175 tokens)

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), 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.

Input parameters:

- `address` (string)
- `chainId` (integer): Default 4663.
- `slug` (string): A project slug, for all of its contracts.

Output parameters:

- `api` (string)
- `data`
- `schema` (string)

### `get_v4_hook` (~70 tokens)

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.

Input parameters:

- `address` (string, required)

Output parameters:

- `api` (string)
- `data`
- `schema` (string)

### `project_diff` (~97 tokens)

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.

Input parameters:

- `from` (string, required)
- `slug` (string, required): A project slug, e.g. "agentos".
- `to` (string, required)

Output parameters:

- `api` (string)
- `data`
- `schema` (string)

### `ask_hey` (~98 tokens)

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.

Input parameters:

- `question` (string, required): The question, in the reader's words.
- `slug` (string, required): A project slug, e.g. "agentos".

Output parameters:

- `api` (string)
- `data`
- `schema` (string)

### `chain_overview` (~131 tokens)

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.

Input parameters:

- `days` (integer): days: 1–400 (default 14); unlocks: 1–365 ahead (default 30).
- `view` (string)
- `week` (string): weekly-report: e.g. 2026-W37.

Output parameters:

- `api` (string)
- `data`
- `schema` (string)

### `market_integrity` (~81 tokens)

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.

Input parameters:

- `slug` (string, required): A project slug, e.g. "agentos".

Output parameters:

- `api` (string)
- `data`
- `schema` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/hey-research-lab-hey-research/heyresearch#diagnostics

## Score history

- 2026-10-24: 81
- 2026-10-23: 81
- 2026-10-22: 80
- 2026-10-21: 80
- 2026-10-20: 79
- 2026-10-19: 79
- 2026-10-18: 79
- 2026-10-17: 78
- 2026-10-16: 23
- 2026-10-15: 77
- 2026-10-14: 77
- 2026-10-13: 77
- 2026-10-12: 77
- 2026-10-11: 76
- 2026-10-10: 76
- 2026-10-05: 35
- 2026-10-04: 73
- 2026-10-03: 73
- 2026-10-02: 73
- 2026-10-01: 73
- 2026-09-30: 75
- 2026-09-29: 74
- 2026-09-28: 74

## Common questions

### 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 hosted endpoint (https://heyresearch.xyz/mcp).

### Is the HEY Research Lab MCP server safe to use?

HEY Research Lab scores 81 out of 100 on VerifyMCP. 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 14 tools: research_answer, find_projects, get_project_snapshot, get_changes, get_project_timeline, and 9 more. Their descriptions and schemas cost roughly 2,554 tokens of context every time the server is loaded.

### Does the HEY Research Lab MCP server require authentication?

No. We connected to HEY Research Lab without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### 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.

## Links

- Remote endpoint: https://heyresearch.xyz/mcp
- Repository: https://github.com/hey-research-lab/hey-research-open
- Website: https://heyresearch.xyz/developers/agents
- Changelog RSS feed: https://verifymcp.io/servers/hey-research-lab-hey-research/heyresearch.xml
- Changelog JSON feed: https://verifymcp.io/servers/hey-research-lab-hey-research/heyresearch.json
- HTML version of this page: https://verifymcp.io/servers/hey-research-lab-hey-research/heyresearch