Remote MCP · Endpoint

Vice City Hub MCP server

No. Vice City Hub answered an MCP handshake 9 hours ago.

UpLast checked 9 hours ago

Server URL

https://lpglkglhjdqnktybksth.supabase.co/functions/v1/agent-api/mcp

The last check completed an MCP handshake.

Registry name
io.github.vicecityhub/vicecityhub
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
1.79 s
Tools exposed
25 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
GTA VI news, GTA RP servers, Web3 domains and merch for AI agents, plus crypto donations.
Listing
From the official MCP registry (active).
Recent checks of Vice City Hub
CheckedResultHandshake
9 hours agoHandshake completed1.79 s
4 days agoHandshake completed916 ms
14 days agoHandshake completed1.09 s
15 days agoHandshake completed1.74 s
15 days agoHandshake completed978 ms
17 days agoHandshake completed1.16 s
18 days agoHandshake completed1.14 s
19 days agoHandshake completed1.20 s
20 days agoHandshake completed1.38 s
21 days agoHandshake completed989 ms
23 days agoHandshake completed999 ms
26 days agoHandshake completed1.11 s
28 days agoHandshake completed1.12 s

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

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