Remote MCP · Endpoint

RideDesk Developer Docs MCP server

No. RideDesk Developer Docs answered an MCP handshake 9 hours ago.

UpLast checked 9 hours 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
164 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Developer docs for building on RideDesk: booking API, widgets, per-account booking MCP. No auth.
Website
https://ridedesk.app/developers
Repository
https://github.com/ridedeskapp/ridedesk
Listing
From the official MCP registry (active).
Recent checks of RideDesk Developer Docs
CheckedResultHandshake
9 hours agoHandshake completed164 ms
2 days agoHandshake completed202 ms
4 days agoHandshake completed162 ms
6 days agoHandshake completed2.11 s
7 days agoHandshake completed220 ms
8 days agoHandshake completed1.66 s
9 days agoHandshake completed200 ms
12 days agoHandshake completed147 ms
14 days agoHandshake completed542 ms
15 days agoHandshake completed227 ms
16 days agoHandshake completed143 ms
18 days agoHandshake completed176 ms
19 days agoHandshake completed140 ms
19 days agoHandshake completed1.73 s
20 days agoHandshake completed152 ms
21 days agoHandshake completed2.19 s
23 days agoHandshake completed1.42 s

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

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.