Remote MCP · Endpoint

HEY Research Lab MCP server

No. HEY Research Lab answered an MCP handshake 6 hours ago.

UpLast checked 6 hours ago

Server URL

https://heyresearch.xyz/mcp

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
808 ms
Tools exposed
14 tools
Uptime, last 30 days
92.9% from 14 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
6 hours agoHandshake completed808 ms
2 days agoHandshake completed814 ms
4 days agoHandshake completed867 ms
6 days agoHandshake completed824 ms
8 days agoHandshake completed798 ms
10 days agoHandshake completed849 ms
12 days agoHandshake completed846 ms
13 days agoHandshake completed933 ms
14 days agoHandshake completed833 ms
15 days agoHandshake completed821 ms
18 days agoHandshake completed280 ms
20 days agoHandshake completed4.87 s
21 days agoHandshake completed793 ms
23 days agoFailed - the request timed out—

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

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.