Prototyp · Vorschau: alle Server aus der offiziellen Registry, alle 30 Minuten synchronisiert. Bewertungen und Benutzerkonten folgen in einem späteren Schritt.
PopNx MCPMCP-Server für alle, die KI nutzen · in einfachen Worten erklärt

HEY Research Lab

von hey-research-labVersion 0.3.3i★ –iComputer oder Cloud
Name in der Registryio.github.hey-research-lab/hey-research

Installieren

Überblick

Beschreibung vom Entwickler (englisches Original)

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

Die drei Säulen von PopNx MCP

Diese drei werden nie zu einer Punktzahl zusammengefasst: Meinungen, Messungen und Beliebtheit sind verschiedene Dinge.

Was du damit machen kannst

Für diesen Server haben wir noch keine Zusammenfassung in einfacher Sprache geschrieben. Unten stehen die Fakten, die wir aus der Registry gelesen haben.

  • Verbindung: Computer oder Cloud
  • Transport: stdio, Streamable HTTP
  • Kategorie: Suche & KI-Gedächtnis
  • Das musst du eintragen: HEY_API_KEY

Installation

Wähle die KI-App, die du nutzt, und kopiere die Einstellungen.

Bevor du installierst

  • Basischecks: 3 von 3 bestanden
  • Läuft auf dem Server des Entwicklers: Was du fragst, läuft über dessen Server.
  • Kann 14 Dinge (Tools) research_answer, find_projects, get_project_snapshot, get_changes …
  • Das trägst du selbst ein: HEY_API_KEY, HEY_MCP_PROFILE

Als geheim markierte Werte sind Schlüssel zu deinem Konto. Gib sie nie weiter und füge sie nie in einen Chat ein.

Du brauchst

  • Läuft in der CloudNichts zu installieren; die Verbindung läuft übers Internet
  • npmNode.js installiert (für den Befehl npx)

Welche App nutzt du?

Wähle oben deine App. Wir merken sie uns, damit der Button beim nächsten Mal „In … installieren“ anzeigt.

Funktioniert in Claude im Web, auf dem Desktop und auf dem Handy:

  1. Öffne Settings → Connectors
  2. Tippe auf Add custom connector
  3. Füge die Adresse unten ein und tippe auf Add
  4. Wenn eine Anmeldung verlangt wird, melde dich beim Dienst des Entwicklers an
SettingsConnectors1+ Add2https://…3
https://heyresearch.xyz/mcp

Oder führ ihn auf deinem Computer aus

Öffne Claude Desktop → Settings → Developer → Edit Config und füge dies in claude_desktop_config.json ein

{
  "mcpServers": {
    "hey-research": {
      "command": "npx",
      "args": [
        "-y",
        "@hey-research-lab/mcp"
      ],
      "env": {
        "HEY_API_KEY": "your-value",
        "HEY_MCP_PROFILE": "your-value"
      }
    }
  }
}

Führe das in deinem Terminal aus

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

Oder führ ihn auf deinem Computer aus

claude mcp add hey-research --env HEY_API_KEY=your-value --env HEY_MCP_PROFILE=your-value -- npx -y @hey-research-lab/mcp

Trag die leeren Werte ein, bevor du ihn startest.

In Cursor öffnen

Oder kopier die Einstellungen selbst

In .cursor/mcp.json in deinem Projekt oder in ~/.cursor/mcp.json einfügen

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

Oder führ ihn auf deinem Computer aus

In Cursor öffnen

Oder kopier die Einstellungen selbst

In .cursor/mcp.json in deinem Projekt oder in ~/.cursor/mcp.json einfügen

{
  "mcpServers": {
    "hey-research": {
      "command": "npx",
      "args": [
        "-y",
        "@hey-research-lab/mcp"
      ],
      "env": {
        "HEY_API_KEY": "your-value",
        "HEY_MCP_PROFILE": "your-value"
      }
    }
  }
}

Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.

In VS Code öffnen

Oder kopier die Einstellungen selbst

In .vscode/mcp.json in deinem Projekt einfügen

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

Oder führ ihn auf deinem Computer aus

In VS Code öffnen

Oder kopier die Einstellungen selbst

In .vscode/mcp.json in deinem Projekt einfügen

{
  "servers": {
    "hey-research": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@hey-research-lab/mcp"
      ],
      "env": {
        "HEY_API_KEY": "your-value",
        "HEY_MCP_PROFILE": "your-value"
      }
    }
  }
}

Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.

ChatGPT verbindet sich nur mit Servern im Internet:

  1. Öffne ChatGPT im Web → Settings → Connectors (Apps)
  2. Tippe auf Create oder Add (bei manchen Tarifen musst du zuerst Developer mode unter Advanced einschalten)
  3. Füge die Adresse unten ein, gib ihr einen Namen und speichere
  4. Wenn eine Anmeldung verlangt wird, melde dich beim Dienst des Entwicklers an
SettingsConnectors1+ Create2https://…3
https://heyresearch.xyz/mcp

Menünamen können sich je nach Tarif und mit der Zeit leicht unterscheiden.

Deine Auswahl bleibt in einem Cookie auf diesem Gerät; kein Konto nötig.

Werte, die du selbst einträgst

  • HEY_API_KEY geheim env
    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_PROFILE env
    Optional: research for the research profile (builder intelligence first); default full.

Diese Einstellungen werden aus dem Registry-Eintrag des Entwicklers erzeugt. Wenn in der README etwas anderes steht, folge der README.

Was er kann

Tool-Namen und -Beschreibungen genau so, wie der Server sie am 6. Nov. 2026 gemeldet hat. Geschrieben hat sie der Entwickler, nicht wir; wir zeigen sie als reinen Text.

  • research_answer

    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 (proj

  • find_projects

    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 a

  • get_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), verificat

  • get_changes

    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

  • get_project_timeline

    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

  • explain_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

  • get_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

  • get_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, s

  • get_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 answ

  • get_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.

  • 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 cau

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

  • 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;

  • 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

Basischecksi

Wir prüfen Informationen, die jeder sehen kann; den Code haben wir nicht gelesen. Checks, die nicht zutreffen, werden nicht mitgezählt. · Geprüft am 7. Nov. 2026

  • ✓ Bestanden

    Entwickler passt zum Repo

    Der Registry-Name wurde mit dem GitHub-Konto hey-research-lab bestätigt, dem das Repo gehört

  • … Noch nicht geprüft

    Wird noch gepflegt

    Dieses Repo haben wir noch nicht von GitHub gelesen

  • … Noch nicht geprüft

    Hat eine Lizenz

    Dieses Repo haben wir noch nicht von GitHub gelesen

  • ✓ Bestanden

    Endpunkt antwortet

    Antwort in 307 ms (HTTP 200)

  • – Nicht zutreffend

    Anmeldung mit OAuth

    Keine Anmeldung nötig

  • ✓ Bestanden

    Keine versteckten Anweisungen in Tool-Beschreibungen

    Wir haben 14 Tool-Beschreibungen gelesen und keine versteckten Anweisungen an die KI gefunden

Im Vergleich mit anderen in Suche & KI-Gedächtnisi

  • Mehr Sterne als 0 % der anderen 5659 Server in dieser Kategorie
  • Neuer in der Registry veröffentlicht als 94 % der anderen 5659 Server in dieser Kategorie
  • Basischecks gleich gut wie oder besser als bei 100 % der anderen 5659 Server in dieser Kategorie

Verglichen mit allen aktiven Servern dieser Kategorie in der Registry. Sterne zählen nur, wenn dem Herausgeber das Repo gehört.

Häufige Fragen

Ist HEY Research Lab sicher?

Er hat 3 von 3 zutreffenden Basischecks bestanden. Den Code haben wir nicht gelesen. Bevor du einen Schlüssel oder Token hinzufügst, sieh nach, welche Zugriffe der Server verlangt, und nutze einen Schlüssel, der nur die Berechtigungen hat, die du brauchst.

Welche Schlüssel oder Codes braucht er?

Das musst du eintragen: HEY_API_KEY

Läuft er auf meinem Computer oder in der Cloud?

Beides geht: Installiere ihn auf deinem Computer oder verbinde dich mit der Cloud-Version.

Wird er noch gepflegt?

Das GitHub-Repo wurde zuletzt – geändert, und die neueste Version (0.3.3) kam vorgestern in die Registry.

Welche Apps können ihn nutzen?

Apps, die MCP unterstützen, etwa Claude Desktop, Claude Code, Cursor und VS Code. Er verbindet sich per URL, also funktionieren auch Apps, die Remote-MCP-Server akzeptieren, zum Beispiel ChatGPT im Entwicklermodus.

Was kann ich stattdessen nutzen?

In derselben Kategorie: Context7, Codebase Memory, Exa

Alternativen

Server derselben Kategorie von anderen Entwicklern, sortiert nach Sternen.

So liest du eine Karte:★ GitHub-SterneiDrei Säulen: Bewertungen · Checks · NutzungiAktualisiert = neueste Version in der Registry veröffentlichti

Context7

von upstash

Up-to-date docs for AI agents

Computer oder Cloud★ 64.224MITAktualisiert gestern
Installieren

Codebase Memory

von DeusData

Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.

Läuft auf deinem Computer★ 48.148MITAktualisiert vor 21 Tagen
Installieren

Exa

von exa-labs

Connect AI agents to Exa for web search, content fetching, and multi-step research.

Läuft in der Cloud★ 5.213MITAktualisiert vor 2 Monaten
Installieren

README vom Entwickler

README öffnen

Unverändert aus dem Repo des Entwicklers übernommen. PopNx MCP hat den Inhalt weder geprüft noch empfiehlt es ihn. HTML, Bilder und Skripte wurden entfernt. Links führen von dieser Website weg.

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

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

Licence

MIT © HEY Research Lab

PopNx fragen