Remote MCP · Endpoint

io.github.pooriaarab/robotaxis MCP server

No. io.github.pooriaarab/robotaxis answered an MCP handshake 28 minutes ago.

UpLast checked 28 minutes ago

Server URL

https://robotaxis.fyi/mcp

The last check completed an MCP handshake.

Registry name
io.github.pooriaarab/robotaxis
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
173 ms
Tools exposed
11 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Where you can ride a robotaxi today, city by city.
Listing
From the official MCP registry (active).
Recent checks of io.github.pooriaarab/robotaxis
CheckedResultHandshake
28 minutes agoHandshake completed173 ms
10 days agoHandshake completed781 ms
11 days agoHandshake completed247 ms
11 days agoHandshake completed157 ms
13 days agoHandshake completed120 ms
14 days agoHandshake completed125 ms
15 days agoHandshake completed155 ms
16 days agoHandshake completed135 ms
17 days agoHandshake completed129 ms
19 days agoHandshake completed566 ms
21 days agoHandshake completed133 ms
24 days agoHandshake completed148 ms
26 days agoHandshake completed1.17 s

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

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 io.github.pooriaarab/robotaxis and makes no claim about it beyond what these checks measured.