Remote MCP · Endpoint

HEY Research Lab MCP server

No. HEY Research Lab answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://heyresearch.xyz/mcp/research

The last check completed an MCP handshake.

Registry name
io.github.hey-research-lab/hey-research
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
787 ms
Tools exposed
8 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Evidence-backed Robinhood Chain research: builders, ships, contracts, changes, market context.
Listing
From the official MCP registry (active).
Recent checks of HEY Research Lab
CheckedResultHandshake
1 hour agoHandshake completed787 ms
2 days agoHandshake completed794 ms
5 days agoHandshake completed785 ms
7 days agoHandshake completed812 ms
9 days agoHandshake completed798 ms
11 days agoHandshake completed783 ms
13 days agoHandshake completed828 ms
15 days agoHandshake completed813 ms
17 days agoHandshake completed819 ms
19 days agoHandshake completed748 ms
20 days agoHandshake completed803 ms
21 days agoHandshake completed771 ms
23 days agoHandshake completed762 ms

The last 13 checks. Full history is kept for 30 days; the all-time counter stands at 13 responding of 13.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with HEY Research Lab and makes no claim about it beyond what these checks measured.