Remote MCP · Endpoint

RideDesk Developer Docs MCP server

No. RideDesk Developer Docs answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://ridedesk.app/api/mcp

The last check completed an MCP handshake.

Registry name
app.ridedesk/docs
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
171 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Developer docs for building on RideDesk: booking API, widgets, per-account booking MCP. No auth.
Listing
From the official MCP registry (active).
Recent checks of RideDesk Developer Docs
CheckedResultHandshake
1 hour agoHandshake completed171 ms
1 day agoHandshake completed501 ms
2 days agoHandshake completed160 ms
3 days agoHandshake completed1.05 s
4 days agoHandshake completed174 ms
5 days agoHandshake completed223 ms
7 days agoHandshake completed459 ms
10 days agoHandshake completed193 ms
12 days agoHandshake completed216 ms
15 days agoHandshake completed1.76 s
17 days agoHandshake completed198 ms
19 days agoHandshake completed1.81 s
21 days agoHandshake completed164 ms
23 days agoHandshake completed202 ms
25 days agoHandshake completed162 ms
26 days agoHandshake completed2.11 s
28 days agoHandshake completed220 ms
29 days agoHandshake completed1.66 s

The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 29 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 RideDesk Developer Docs and makes no claim about it beyond what these checks measured.