Remote MCP · Endpoint

Transport Nsw MCP server

No. Transport Nsw answered an MCP handshake 59 minutes ago.

UpLast checked 59 minutes ago

Server URL

https://gateway.pipeworx.io/transport-nsw/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/transport-nsw
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
56 ms
Tools exposed
48 tools
Uptime, last 30 days
92.9% from 14 checks
Described by its publisher as
Transport for NSW MCP — journey planning, live departures, service alerts and commuter car-park…
Listing
From the official MCP registry (active).
Recent checks of Transport Nsw
CheckedResultHandshake
59 minutes agoHandshake completed56 ms
9 days agoHandshake completed96 ms
10 days agoHandshake completed133 ms
11 days agoHandshake completed88 ms
12 days agoHandshake completed118 ms
14 days agoHandshake completed92 ms
15 days agoHandshake completed103 ms
15 days agoHandshake completed94 ms
17 days agoHandshake completed100 ms
19 days agoHandshake completed191 ms
21 days agoFailed - the request timed out—
24 days agoHandshake completed68 ms
26 days agoHandshake completed52 ms
28 days agoHandshake completed60 ms

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

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