Remote MCP · Endpoint

HEY Research Lab MCP server

No. HEY Research Lab answered an MCP handshake 34 minutes ago.

UpLast checked 34 minutes 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
796 ms
Tools exposed
14 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
The public record of building on Robinhood Chain — every ship with its source.
Listing
From the official MCP registry (active).
Recent checks of HEY Research Lab
CheckedResultHandshake
34 minutes agoHandshake completed796 ms
8 days agoHandshake completed785 ms
9 days agoHandshake completed826 ms
11 days agoHandshake completed821 ms
12 days agoHandshake completed810 ms
12 days agoHandshake completed318 ms
14 days agoHandshake completed838 ms
14 days agoHandshake completed832 ms
16 days agoHandshake completed880 ms
19 days agoHandshake completed765 ms
21 days agoHandshake completed772 ms
24 days agoHandshake completed808 ms
26 days agoHandshake completed814 ms
28 days agoHandshake completed867 ms

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

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.