Remote MCP · Endpoint

ServGhost MCP server

No. ServGhost answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://servghost.com/mcp

The last check completed an MCP handshake.

Registry name
com.servghost/servghost
Transport
Streamable HTTP
Protocol negotiated
2025-03-26
Handshake latency
350 ms
Tools exposed
11 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Rent offshore VPS, dedicated, RDP and GPU servers in 7 jurisdictions; crypto-only, no KYC
Listing
From the official MCP registry (active).
Recent checks of ServGhost
CheckedResultHandshake
1 hour agoHandshake completed350 ms
2 days agoHandshake completed429 ms
4 days agoHandshake completed346 ms
5 days agoHandshake completed463 ms
7 days agoHandshake completed369 ms
8 days agoHandshake completed351 ms
9 days agoHandshake completed350 ms
12 days agoHandshake completed370 ms
13 days agoHandshake completed456 ms
15 days agoHandshake completed337 ms
16 days agoHandshake completed406 ms
17 days agoHandshake completed442 ms
19 days agoHandshake completed397 ms
20 days agoHandshake completed402 ms
20 days agoHandshake completed404 ms
21 days agoHandshake completed400 ms
22 days agoHandshake completed476 ms

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

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