Remote MCP · Endpoint

Relvato MCP server

No. Relvato answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://app.relvato.com/api/mcp

The last check completed an MCP handshake.

Registry name
com.relvato/relvato
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
209 ms
Tools exposed
58 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Website monitoring: add sites, configure and run monitors, read health, review results, apply fixes.
Listing
From the official MCP registry (active).
Recent checks of Relvato
CheckedResultHandshake
1 hour agoHandshake completed209 ms
2 days agoHandshake completed428 ms
4 days agoHandshake completed1.07 s
6 days agoHandshake completed2.67 s
8 days agoHandshake completed199 ms
10 days agoHandshake completed1.06 s
12 days agoHandshake completed213 ms
14 days agoHandshake completed250 ms
15 days agoHandshake completed998 ms
16 days agoHandshake completed211 ms
18 days agoHandshake completed231 ms
20 days agoHandshake completed210 ms
22 days agoHandshake completed177 ms
24 days agoHandshake completed239 ms
25 days agoHandshake completed324 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 Relvato and makes no claim about it beyond what these checks measured.