Remote MCP · Endpoint

Relvato MCP server

No. Relvato answered an MCP handshake 34 minutes ago.

UpLast checked 34 minutes 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
184 ms
Tools exposed
58 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Website monitoring: uptime, checkout, SEO (Search Console, Bing), security, speed, DNS, compliance.
Listing
From the official MCP registry (active).
Recent checks of Relvato
CheckedResultHandshake
34 minutes agoHandshake completed184 ms
8 days agoHandshake completed239 ms
9 days agoHandshake completed185 ms
11 days agoHandshake completed345 ms
12 days agoHandshake completed234 ms
12 days agoHandshake completed305 ms
14 days agoHandshake completed208 ms
14 days agoHandshake completed204 ms
16 days agoHandshake completed239 ms
19 days agoHandshake completed215 ms
21 days agoHandshake completed209 ms
24 days agoHandshake completed428 ms
26 days agoHandshake completed1.07 s
28 days agoHandshake completed2.67 s

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 25 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 Relvato and makes no claim about it beyond what these checks measured.