HEY Research Lab
REMOTE · HEYRESEARCH.XYZ · 3 COMPONENTS
Evidence-backed Robinhood Chain research: builders, ships, contracts, changes, market context.
Available components
Last scanned (23 hours ago)
Scores higher than 84% of remote servers
Reachable. Last reached 23 Oct 2026.
Category Crypto and Web3
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. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability71
- 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 2221 tokens (~246/item across 9 items; 8 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 Management60
- Stability observed for 18 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage86
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 50% 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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 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.
- 23 Oct 26 0
- Tool “research_answer” rewrote its description, which is the text the model reads security
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Oct 26 +1
- Tool “explain_fact” rewrote its description, which is the text the model reads security
- “explain_fact” added an optional parameter “event” cosmetic
- 18 Oct 26 +1
- 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
- 17 Oct 26 0
- Server version: 0.3.1 → 0.3.2 functional
- “find_projects” reworded the description of “query” cosmetic
- 16 Oct 26 +1
- 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
- Server version: 0.3.0 → 0.3.1 functional
- 14 Oct 26 0
- 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
- Schema quality: 195 → 225 ▼ functional
- Server version: 0.2.0 → 0.3.0 functional
- “research_answer” added an optional parameter “detail” cosmetic
- “research_answer” added an optional parameter “q” cosmetic
- 13 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “find_projects” 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 “get_evidence” 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 “get_v4_hook” rewrote its description, which is the text the model reads security
- Tool “research_answer” 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_changes” rewrote its description, which is the text the model reads security
- “find_projects” reworded the description of “query” cosmetic
- Tool “find_projects” changed its title: Find projects → Find a Robinhood Chain project cosmetic
- Tool “get_contract” changed its title: Contract → Who made this contract cosmetic
- Tool “research_answer” changed its title: Agent research answer → Research a Robinhood Chain project cosmetic
- Tool “get_project_timeline” changed its title: Project timeline → What a project shipped cosmetic
- Tool “get_changes” changed its title: What changed → What changed on Robinhood Chain cosmetic
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 23 Oct 2026 · Probed https://heyresearch.xyz/mcp/research
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=heyresearch.xyz | CN=WE1,O=Google Trust Services,C=US | 1 Sept 2026 | 30 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 67f594a6c88d69900ea45aa9171b5791 |
| SANs: heyresearch.xyz, *.heyresearch.xyz | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of heyresearch.xyz. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| xyz. | present | 3599, 18130 | 8, 8 | Verified |
| heyresearch.xyz. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'self'; script-src 'self' 'nonce-O+3oAdkEeCnjBZ+a/nFYPA==' 'sha256-447vZuxY3+0LsIVO0SP2yGBxlwsRUUZl6Po0ndgwRq4=' 'strict-dynamic'; style-src 'self' 'unsafe-inline'; img-src 'self' data: blob: https:; font-src 'self' data:; connect-src 'self' https://*.walletconnect.com wss://*.walletconnect.com https://*.walletconnect.org wss://*.walletconnect.org https://*.web3modal.org https://*.reown.com https://*.coinbase.com wss://*.coinbase.com https://rpc.mainnet.chain.robinhood.com https://robinhoodchain.blockscout.com; frame-src 'self' https://verify.walletconnect.com https://verify.walletconnect.org https://secure.walletconnect.com https://secure.walletconnect.org https://keys.coinbase.com; worker-src 'self' blob:; manifest-src 'self'; object-src 'none'; base-uri 'self'; form-action 'self' https://github.com; frame-ancestors 'none'; upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=(), usb=(), interest-cohort=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://heyresearch.xyz/mcp/research | Verified | 200 | |
| http (plaintext) | http://heyresearch.xyz/mcp/research | HTTPS enforced | 308 | https://heyresearch.xyz/mcp/research |
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 →
explain_fact Explain a fact ~177
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.
| Name | Type | Req | Description |
|---|---|---|---|
| event | string | – | With fact=build.change: a change-ledger id; omit for the latest. |
| 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 ~111
Which Robinhood Chain project is this name, $TICKER or 0x contract? Identity only (name, ticker, contract, slug), at most eight rows; give the slug to research_answer. A full 0x address answers whether anyone is building that contract: activity status, ship records in 30 days, the last ship with its source, whether the project names it.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Name, $TICKER, slug or 0x contract; q also works. |
| Name | Type | Req | Description |
|---|---|---|---|
| api | string | yes | – |
| data | – | – | – |
| schema | string | yes | – |
No examples provided.
get_changes What changed on Robinhood Chain ~257
What changed on Robinhood Chain today or this week, or for one project or contract? The change ledger without market readings: 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.
| 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 ~125
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:, 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.
| 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_timeline What a project shipped ~120
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: build (default), code, onchain, 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_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.
research_answer Research a Robinhood Chain project ~207
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.
| 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 | – | – | – |
| 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 is a hosted endpoint at https://heyresearch.xyz/mcp/research, 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.
remote · heyresearch.xyz
claude mcp add --transport http hey-research-lab-hey-research 'https://heyresearch.xyz/mcp/research'
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/research).
Is the HEY Research Lab MCP server safe to use?
HEY Research Lab scores 80 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 8 tools: research_answer, find_projects, get_changes, get_project_timeline, explain_fact, and 3 more. Their descriptions and schemas cost roughly 1,242 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 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.