Remote MCP · Endpoint

Straelo Relay MCP server

No. Straelo Relay answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://relay.straelo.com/mcp/

The last check completed an MCP handshake.

Registry name
com.straelo/relay
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
108 ms
Tools exposed
12 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
MCP tools for agents: web research, content extraction, email, DNS, and blockchain intelligence.
Listing
From the official MCP registry (active).
Recent checks of Straelo Relay
CheckedResultHandshake
1 hour agoHandshake completed108 ms
2 days agoHandshake completed117 ms
4 days agoHandshake completed92 ms
6 days agoHandshake completed91 ms
8 days agoHandshake completed103 ms
10 days agoHandshake completed104 ms
11 days agoHandshake completed103 ms
13 days agoHandshake completed98 ms
14 days agoHandshake completed93 ms
15 days agoHandshake completed103 ms
18 days agoHandshake completed95 ms
19 days agoHandshake completed104 ms
21 days agoHandshake completed90 ms
22 days agoHandshake completed96 ms
23 days agoHandshake completed96 ms

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

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