RideDesk Developer Docs
REMOTE · RIDEDESK.APP · SCANNED SEP 21
Developer docs for building on RideDesk: booking API, widgets, per-account booking MCP. No auth.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 486 tokens (~97/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (40% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the RideDesk Developer Docs MCP server?
RideDesk Developer Docs is a hosted endpoint at https://ridedesk.app/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · ridedesk.app
claude mcp add --transport http app-ridedesk-docs 'https://ridedesk.app/api/mcp'
{
"mcpServers": {
"app-ridedesk-docs": {
"url": "https://ridedesk.app/api/mcp"
}
}
} {
"servers": {
"app-ridedesk-docs": {
"type": "http",
"url": "https://ridedesk.app/api/mcp"
}
}
} [mcp_servers.app-ridedesk-docs] url = "https://ridedesk.app/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"app-ridedesk-docs": {
"type": "remote",
"url": "https://ridedesk.app/api/mcp",
"enabled": true
}
}
} openclaw mcp add app-ridedesk-docs --url 'https://ridedesk.app/api/mcp' --transport streamable-http
mcp_servers:
app-ridedesk-docs:
url: "https://ridedesk.app/api/mcp" {
"McpServers": {
"app-ridedesk-docs": {
"Transport": "http",
"Url": "https://ridedesk.app/api/mcp"
}
}
} assistant mcp add app-ridedesk-docs -t streamable-http -u 'https://ridedesk.app/api/mcp'
{
"mcpServers": {
"app-ridedesk-docs": {
"type": "http",
"url": "https://ridedesk.app/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 18 Sept 26 0
- Stability: 0.97 → pass security
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Sept 2026 · Probed https://ridedesk.app/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=ridedesk.app | CN=WE1,O=Google Trust Services,C=US | 21 Aug 2026 | 19 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 3a4d9736c23dd32a1332da7ae8879d8d |
| SANs: ridedesk.app, *.ridedesk.app | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of ridedesk.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| ridedesk.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains |
| content-security-policy | default-src 'self'; base-uri 'self'; frame-ancestors 'none'; frame-src 'self' https://ridedesk-demo-transfers.ridedesk.app; object-src 'none'; form-action 'self'; img-src 'self' data: blob: https:; font-src 'self' data:; style-src 'self' 'unsafe-inline'; script-src 'self' 'unsafe-inline' 'unsafe-eval'; connect-src 'self' https://*.supabase.co wss://*.supabase.co; manifest-src 'self'; worker-src 'self' blob:; upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | no-referrer |
| permissions-policy | camera=(), microphone=(self), geolocation=(), browsing-topics=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://ridedesk.app/api/mcp | Verified | 200 | |
| http (plaintext) | http://ridedesk.app/api/mcp | HTTPS enforced | 301 | https://ridedesk.app/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_doc Read a documentation topic ~89
One documentation topic as markdown: the booking API contract, checkout, widgets, attribution, live chat, the customer portal, or the per-account booking MCP server.
| Name | Type | Req | Description |
|---|---|---|---|
| host | string | – | The operator's RideDesk domain (e.g. their-workspace.ridedesk.app or a custom domain). Optional — examples use a placeholder without it. |
| topic | string | yes | A topic from list_docs |
No output schema declared.
No examples provided.
get_integration_brief Get the integration brief ~83
A self-contained brief for a coding agent building a transfer-booking website on the RideDesk API — the flow, the rules the server enforces, and the acceptance criteria.
| Name | Type | Req | Description |
|---|---|---|---|
| host | string | – | The operator's RideDesk domain (e.g. their-workspace.ridedesk.app or a custom domain). Optional — examples use a placeholder without it. |
No output schema declared.
No examples provided.
get_widget_snippets Get widget & tag snippets ~76
Copy-paste tags: the attribution script, the live-chat script, and the embeddable booking/enquiry/rental widget iframes.
| Name | Type | Req | Description |
|---|---|---|---|
| host | string | – | The operator's RideDesk domain (e.g. their-workspace.ridedesk.app or a custom domain). Optional — examples use a placeholder without it. |
No output schema declared.
No examples provided.
list_docs List documentation topics ~24
The available documentation topics with one-line summaries. Call first, then get_doc.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| docs | array | yes | Every documentation topic this server can serve. |
| note | string | yes | – |
No examples provided.
search_docs Search the documentation ~101
Keyword search across all documentation topics. Returns matching sections with excerpts; follow up with get_doc for the full topic.
| Name | Type | Req | Description |
|---|---|---|---|
| host | string | – | The operator's RideDesk domain (e.g. their-workspace.ridedesk.app or a custom domain). Optional — examples use a placeholder without it. |
| query | string | yes | Keywords, an endpoint path, or a field name (e.g. "quote_ref", "apple pay", "/api/enquiries") |
| Name | Type | Req | Description |
|---|---|---|---|
| note | string | – | Present only when there were no matches. |
| results | array | yes | Matching sections, best first. Empty when nothing matched. |
No examples provided.
What is the RideDesk Developer Docs MCP server?
RideDesk Developer Docs is an MCP server listed in the public MCP registry as app.ridedesk/docs. Developer docs for building on RideDesk: booking API, widgets, per-account booking MCP. No auth. This page covers its hosted endpoint (https://ridedesk.app/api/mcp).
Is the RideDesk Developer Docs MCP server safe to use?
RideDesk Developer Docs scores 88 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the RideDesk Developer Docs MCP server expose?
RideDesk Developer Docs exposes 5 tools: list_docs, get_doc, search_docs, get_integration_brief, get_widget_snippets. Their descriptions and schemas cost roughly 373 tokens of context every time the server is loaded.
Does the RideDesk Developer Docs MCP server require authentication?
No. We connected to RideDesk Developer Docs without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the RideDesk Developer Docs MCP server still maintained?
RideDesk Developer Docs is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.