Remote MCP · Endpoint

SG Parking Live MCP server

No. SG Parking Live answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://sg-parking-live.rowb.app/mcp

The last check completed an MCP handshake.

Registry name
app.rowb.sg-parking-live/carpark-availability
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
448 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Live HDB carpark availability for Singapore from the official data.gov.sg feed.
Listing
From the official MCP registry (active).
Recent checks of SG Parking Live
CheckedResultHandshake
1 hour agoHandshake completed448 ms
2 days agoHandshake completed410 ms
5 days agoHandshake completed574 ms
7 days agoHandshake completed446 ms
9 days agoHandshake completed564 ms
11 days agoHandshake completed490 ms
13 days agoHandshake completed519 ms
15 days agoHandshake completed454 ms
17 days agoHandshake completed414 ms
19 days agoHandshake completed435 ms
20 days agoHandshake completed489 ms
21 days agoHandshake completed412 ms
23 days agoHandshake completed445 ms
25 days agoHandshake completed455 ms

The last 14 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 SG Parking Live and makes no claim about it beyond what these checks measured.