HEY Research Lab
Resumen
Descripción del creador (original en inglés)
The public record of building on Robinhood Chain — every ship with its source.
Los tres pilares de PopNx MCP
Estos tres nunca se combinan en una sola puntuación: las opiniones, las mediciones y la popularidad son cosas distintas.
- Opinión de usuariosiAún no hay reseñasLas reseñas se abrirán junto con las cuentas en una etapa posterior
- Nuestras revisiones básicasi3 de 3 superadasRevisado con información pública; el código aún no se ha escaneado
- UsoiMuy nuevo↓ 287/sem · ★ –
Qué puedes hacer con él
Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.
- Conexión: Computadora o nube
- Transporte: stdio, Streamable HTTP
- Categoría: Búsqueda y memoria de IA
- Debes completar: HEY_API_KEY
Instalación
Elige la app de IA que usas y copia la configuración.
Antes de instalar
- Revisiones básicas: 3 de 3 superadas
- Se ejecuta en el servidor del creador: lo que le pidas pasa por su servidor.
- Puede hacer 14 cosas (herramientas) research_answer, find_projects, get_project_snapshot, get_changes …
- Debes completar tú:
HEY_API_KEY,HEY_MCP_PROFILE
Los valores marcados como secretos son llaves de tu cuenta. Nunca los compartas ni los pegues en un chat.
Necesitas
- Se ejecuta en la nubeNo hay nada que instalar; se conecta por internet
- npmNode.js instalado (para el comando npx)
¿Qué app usas?
Elige tu app arriba. La recordamos, así que la próxima vez el botón dirá “Instalar en …”.
Funciona en Claude para web, escritorio y móvil:
- Abre Settings → Connectors
- Presiona Add custom connector
- Pega la dirección de abajo y presiona Add
- Si te pide iniciar sesión, inicia sesión en el servicio del creador
https://heyresearch.xyz/mcpO ejecútalo en tu computadora
Abre Claude Desktop → Settings → Developer → Edit Config y pega esto en claude_desktop_config.json
{
"mcpServers": {
"hey-research": {
"command": "npx",
"args": [
"-y",
"@hey-research-lab/mcp"
],
"env": {
"HEY_API_KEY": "your-value",
"HEY_MCP_PROFILE": "your-value"
}
}
}
}Ejecuta esto en tu terminal
claude mcp add --transport http hey-research https://heyresearch.xyz/mcpO ejecútalo en tu computadora
claude mcp add hey-research --env HEY_API_KEY=your-value --env HEY_MCP_PROFILE=your-value -- npx -y @hey-research-lab/mcpCompleta los valores vacíos antes de ejecutarlo.
O copia la configuración tú
Pégalo en .cursor/mcp.json de tu proyecto, o en ~/.cursor/mcp.json
{
"mcpServers": {
"hey-research": {
"url": "https://heyresearch.xyz/mcp"
}
}
}O ejecútalo en tu computadora
O copia la configuración tú
Pégalo en .cursor/mcp.json de tu proyecto, o en ~/.cursor/mcp.json
{
"mcpServers": {
"hey-research": {
"command": "npx",
"args": [
"-y",
"@hey-research-lab/mcp"
],
"env": {
"HEY_API_KEY": "your-value",
"HEY_MCP_PROFILE": "your-value"
}
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
O copia la configuración tú
Pégalo en .vscode/mcp.json de tu proyecto
{
"servers": {
"hey-research": {
"type": "http",
"url": "https://heyresearch.xyz/mcp"
}
}
}O ejecútalo en tu computadora
O copia la configuración tú
Pégalo en .vscode/mcp.json de tu proyecto
{
"servers": {
"hey-research": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@hey-research-lab/mcp"
],
"env": {
"HEY_API_KEY": "your-value",
"HEY_MCP_PROFILE": "your-value"
}
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
ChatGPT solo se conecta a servidores en internet:
- Abre ChatGPT en la web → Settings → Connectors (Apps)
- Presiona Create o Add (en algunos planes primero hay que activar Developer mode en Advanced)
- Pega la dirección de abajo, ponle un nombre y guarda
- Si te pide iniciar sesión, inicia sesión en el servicio del creador
https://heyresearch.xyz/mcpLos nombres de los menús pueden variar un poco según el plan y con el tiempo.
Tu elección se guarda en una cookie en este dispositivo; no necesitas cuenta.
Valores que debes completar
- Optional HEY API key: names your integration and gives it its own per-minute bucket with a monthly allowance; a free key keeps the anonymous per-minute figure. Nothing private is behind it.
HEY_MCP_PROFILEenvOptional: research for the research profile (builder intelligence first); default full.
Esta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.
Qué puede hacer
Nombres y descripciones de las herramientas tal como los informó el servidor el 6 nov 2026. Los escribió el creador, no nosotros; los mostramos como texto sin formato.
research_answerIs 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 (proj
find_projectsWhich 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 a
get_project_snapshotWhere 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), verificat
get_changesWhat 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
get_project_timelineWhat 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
explain_factWhy 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
get_evidenceWhat 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
get_token_marketDoes 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, s
get_contractWho 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 answ
get_v4_hookWho 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.
project_diffWhat 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 cau
ask_heyAsking 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.
chain_overviewHow 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;
market_integrityWhat 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
Revisiones básicasi
Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 8 nov 2026
- ✓ Superada
El creador coincide con el repo
El nombre en el registro se verificó con la cuenta de GitHub hey-research-lab, dueña del repo
- … Aún sin revisar
Sigue en mantenimiento
Todavía no hemos leído este repo en GitHub
- … Aún sin revisar
Tiene licencia
Todavía no hemos leído este repo en GitHub
- ✓ Superada
El endpoint responde
Respondió en 307 ms (HTTP 200)
- – No aplica
Inicio de sesión con OAuth
No hace falta iniciar sesión
- ✓ Superada
Sin instrucciones ocultas en las descripciones de herramientas
Leímos 14 descripciones de herramientas y no encontramos instrucciones ocultas para la IA
Comparado con otros en Búsqueda y memoria de IAi
- Más estrellas que el 0% de los otros 5684 servidores de esta categoría
- Publicado en el registro más recientemente que el 93% de los otros 5684 servidores de esta categoría
- Revisiones básicas iguales o mejores que el 100% de los otros 5684 servidores de esta categoría
Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.
Preguntas frecuentes
¿Es seguro HEY Research Lab?
Superó 3 de 3 revisiones básicas aplicables. No hemos leído el código. Antes de agregar una clave o un token, revisa qué acceso pide el servidor y usa una clave que tenga solo los permisos que necesitas.
¿Qué claves o códigos necesita?
Debes completar: HEY_API_KEY
¿Se ejecuta en mi computadora o en la nube?
Funciona de las dos formas: instálalo en tu computadora o conéctate a la versión en la nube.
¿Sigue en mantenimiento?
El repo de GitHub cambió por última vez –, y la última versión (0.3.3) llegó al registro hace 3 días.
¿Qué apps pueden usarlo?
Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. Se conecta por URL, así que también funcionan las apps que aceptan servidores MCP remotos, como ChatGPT en modo desarrollador.
¿Qué puedo usar en su lugar?
En la misma categoría: Context7, Codebase Memory, Exa
Alternativas
Servidores de la misma categoría hechos por otros creadores, ordenados por estrellas.
Cómo leer una tarjeta:↓ Descargas por semanai★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi
Codebase Memory
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
Exa
Connect AI agents to Exa for web search, content fetching, and multi-step research.
README del creador
Abrir el README
Copiado tal cual del repo del creador. PopNx MCP no lo ha revisado ni lo respalda. Se quitaron HTML, imágenes y scripts. Los enlaces llevan fuera de este sitio.
@hey-research-lab/mcp
npx -y @hey-research-lab/mcp@0.3.3 # 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
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)
npx -y @hey-research-lab/mcp@0.3.3
Node 20 or newer — the floor @modelcontextprotocol/sdk brings with it.
Claude Code
claude mcp add hey-research -- npx -y @hey-research-lab/mcp@0.3.3
Claude Desktop — in claude_desktop_config.json:
{
"mcpServers": { "hey-research": { "command": "npx", "args": ["-y", "@hey-research-lab/mcp@0.3.3"] } } }
Environment
| Variable | Purpose |
|---|---|
HEY_API_URL | Another 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_KEY | An 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_INTEGRITY | Set 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_PROFILE | research 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
| Tool | What it answers |
|---|---|
find_projects | Find 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_snapshot | One 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_changes | The 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_timeline | One project's evidence on one axis, paged with a cursor. |
explain_fact | Why HEY shows a figure: the rule, the source, the inputs, the lineage, the evidence ids. |
get_evidence | One 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_market | One 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_contract | A 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_hook | Who 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_diff | What changed for one project between two dates, never a cause. |
ask_hey | A free-text question about one project, answered only from HEY's record. |
chain_overview | The chain day by day, this week, an archived weekly report, scheduled HoodLock unlocks, or Build Momentum beside market attention. |
research_answer | HEY'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.
pnpm --filter @hey-research-lab/mcp build && node apps/mcp/dist/index.js
Licence
MIT © HEY Research Lab