Context7
Up-to-date docs for AI agents
제작자가 쓴 설명(영어 원문)
The public record of building on Robinhood Chain — every ship with its source.
이 세 가지는 절대 하나의 점수로 합치지 않아요. 의견, 측정, 인기는 서로 다른 것이니까요.
이 서버는 아직 쉬운 말로 된 요약을 쓰지 못했어요. 아래는 레지스트리에서 읽어 온 사실이에요.
쓰고 있는 AI 앱을 고른 다음 설정을 복사하세요.
HEY_API_KEY, HEY_MCP_PROFILE비밀로 표시된 값은 내 계정의 열쇠예요. 절대 다른 사람과 공유하거나 채팅에 붙여 넣지 마세요.
필요한 것
어떤 앱을 쓰세요?
위에서 앱을 고르세요. 기억해 두었다가 다음부터는 버튼에 “…에 설치”라고 표시해요.
웹, 데스크톱, 모바일의 Claude에서 쓸 수 있어요:
https://heyresearch.xyz/mcpClaude Desktop → Settings → Developer → Edit Config를 열고 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"
}
}
}
}터미널에서 이 명령어를 실행하세요
claude mcp add --transport http hey-research https://heyresearch.xyz/mcpclaude mcp add hey-research --env HEY_API_KEY=your-value --env HEY_MCP_PROFILE=your-value -- npx -y @hey-research-lab/mcp실행하기 전에 빈 값을 채워 주세요.
프로젝트의 .cursor/mcp.json 또는 ~/.cursor/mcp.json에 붙여 넣으세요
{
"mcpServers": {
"hey-research": {
"url": "https://heyresearch.xyz/mcp"
}
}
}프로젝트의 .cursor/mcp.json 또는 ~/.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"
}
}
}
}브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.
프로젝트의 .vscode/mcp.json에 붙여 넣으세요
{
"servers": {
"hey-research": {
"type": "http",
"url": "https://heyresearch.xyz/mcp"
}
}
}프로젝트의 .vscode/mcp.json에 붙여 넣으세요
{
"servers": {
"hey-research": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@hey-research-lab/mcp"
],
"env": {
"HEY_API_KEY": "your-value",
"HEY_MCP_PROFILE": "your-value"
}
}
}
}브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.
ChatGPT는 인터넷에 있는 서버에만 연결할 수 있어요:
https://heyresearch.xyz/mcp메뉴 이름은 요금제나 시기에 따라 조금 다를 수 있어요.
선택한 앱은 이 기기의 쿠키에만 저장돼요. 계정은 필요 없어요.
HEY_MCP_PROFILE env이 설정은 제작자의 레지스트리 정보로 만들었어요. README와 다르면 README를 따르세요.
도구 이름과 설명은 서버가 2026년 11월 6일에 알려 준 그대로예요. 우리가 아니라 제작자가 쓴 글이고, 일반 텍스트로만 보여 드려요.
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
누구나 볼 수 있는 정보를 점검했고, 코드는 읽지 않았어요. 해당하지 않는 항목은 개수에서 뺐어요. · 2026년 11월 8일 점검
레지스트리 이름이 GitHub 계정 hey-research-lab 기준으로 확인되었고, 이 계정이 저장소를 소유하고 있어요
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
307ms 만에 응답(HTTP 200)
로그인 필요 없음
도구 설명 14개를 읽었고, AI에게 보내는 숨겨진 지시는 없었어요
레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.
해당하는 기본 점검 3개 중 3개를 통과했어요. 코드는 읽지 않았어요. 키나 토큰을 넣기 전에 서버가 어떤 권한을 요구하는지 확인하고, 꼭 필요한 권한만 있는 키를 쓰세요.
입력해야 할 값: HEY_API_KEY
둘 다 가능해요. 내 컴퓨터에 설치해도 되고, 클라우드 버전에 연결해도 돼요.
GitHub 저장소는 마지막으로 – 변경됐고, 최신 버전(0.3.3)은 그저께 레지스트리에 올라왔어요.
Claude Desktop, Claude Code, Cursor, VS Code처럼 MCP를 지원하는 앱에서 쓸 수 있어요. URL로 연결되기 때문에, 원격 MCP 서버를 지원하는 앱(예: 개발자 모드의 ChatGPT)에서도 쓸 수 있어요.
같은 카테고리에는: Context7, Codebase Memory, Exa
같은 카테고리에서 다른 제작자가 만든 서버예요. 스타 순으로 정렬했어요.
카드 보는 법:★ GitHub 스타i세 기둥: 리뷰 · 점검 · 사용 정도i업데이트 = 최신 버전을 레지스트리에 공개한 날i
Up-to-date docs for AI agents
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
Connect AI agents to Exa for web search, content fetching, and multi-step research.
제작자의 저장소에서 쓰인 그대로 가져왔어요. PopNx MCP가 검토하거나 보증한 내용이 아니에요. HTML, 이미지, 스크립트는 제거했어요. 링크를 누르면 이 사이트를 벗어나요.
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.
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.
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"] } } }
| 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. |
| 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.
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.
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
MIT © HEY Research Lab