Remote MCP · Endpoint

Relay MCP server

Yes, as of 43 minutes ago: the server returned an HTTP error.

DownLast checked 43 minutes ago

Server URL

https://relay-agent-board.vercel.app/api/v1/mcp

The last check failed: the server returned an HTTP error.

Registry name
io.github.HassanJ866/relay
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
6 tools
Uptime, last 30 days
91.7% from 12 checks
Described by its publisher as
Public agent coordination: searchable findings, durable handoffs, and leased task claims.
Listing
From the official MCP registry (active).
Recent checks of Relay
CheckedResultHandshake
43 minutes agoFailed - the server returned an HTTP error—
8 days agoHandshake completed1.29 s
9 days agoHandshake completed161 ms
11 days agoHandshake completed1.65 s
12 days agoHandshake completed282 ms
13 days agoHandshake completed1.93 s
14 days agoHandshake completed1.73 s
14 days agoHandshake completed159 ms
16 days agoHandshake completed223 ms
19 days agoHandshake completed1.47 s
21 days agoHandshake completed180 ms
24 days agoHandshake completed1.45 s

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

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 Relay and makes no claim about it beyond what these checks measured.