# RideDesk Developer Docs (remote · ridedesk.app)

Developer docs for building on RideDesk: booking API, widgets, per-account booking MCP. No auth.

- Trust score: 88/100 (high trust)
- Change this week: +1
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- remote · `ridedesk.app`: 88/100 (this document), [markdown](https://verifymcp.io/servers/app-ridedesk-docs/api-mcp.md), [page](https://verifymcp.io/servers/app-ridedesk-docs/api-mcp)

## Channel facts

- Endpoint: `https://ridedesk.app/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.3`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-21.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 80/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 486 tokens (~97/item across 5 items; 5 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (40% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### 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.

### Claude

```bash
claude mcp add --transport http app-ridedesk-docs 'https://ridedesk.app/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "app-ridedesk-docs": {
      "url": "https://ridedesk.app/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "app-ridedesk-docs": {
      "type": "http",
      "url": "https://ridedesk.app/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.app-ridedesk-docs]
url = "https://ridedesk.app/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "app-ridedesk-docs": {
      "type": "remote",
      "url": "https://ridedesk.app/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add app-ridedesk-docs --url 'https://ridedesk.app/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  app-ridedesk-docs:
    url: "https://ridedesk.app/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "app-ridedesk-docs": {
      "Transport": "http",
      "Url": "https://ridedesk.app/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add app-ridedesk-docs -t streamable-http -u 'https://ridedesk.app/api/mcp'
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-18 (score 88, 0)

- [security] Stability: 0.97 → pass

### 2026-09-17 (score 88, +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.

### 2026-09-14 (score 87, +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.

### 2026-09-12 (score 86, +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.

### 2026-09-10 (score 85, +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.

### 2026-09-08 (score 84, +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.

### 2026-09-06 (score 83, +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.

### 2026-09-04 (score 82, +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.

## MCP tools (5)

### `list_docs` (~24 tokens)

List documentation topics

The available documentation topics with one-line summaries. Call first, then get_doc.

Output parameters:

- `docs` (array): Every documentation topic this server can serve.
- `note` (string)

### `get_doc` (~89 tokens)

Read a documentation topic

One documentation topic as markdown: the booking API contract, checkout, widgets, attribution, live chat, the customer portal, or the per-account booking MCP server.

Input parameters:

- `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, required): A topic from list_docs

### `search_docs` (~101 tokens)

Search the documentation

Keyword search across all documentation topics. Returns matching sections with excerpts; follow up with get_doc for the full topic.

Input parameters:

- `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, required): Keywords, an endpoint path, or a field name (e.g. "quote_ref", "apple pay", "/api/enquiries")

Output parameters:

- `note` (string): Present only when there were no matches.
- `results` (array): Matching sections, best first. Empty when nothing matched.

### `get_integration_brief` (~83 tokens)

Get the integration brief

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.

Input parameters:

- `host` (string): The operator's RideDesk domain (e.g. their-workspace.ridedesk.app or a custom domain). Optional — examples use a placeholder without it.

### `get_widget_snippets` (~76 tokens)

Get widget & tag snippets

Copy-paste tags: the attribution script, the live-chat script, and the embeddable booking/enquiry/rental widget iframes.

Input parameters:

- `host` (string): The operator's RideDesk domain (e.g. their-workspace.ridedesk.app or a custom domain). Optional — examples use a placeholder without it.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/app-ridedesk-docs/api-mcp#diagnostics

## Score history

- 2026-09-21: 88
- 2026-09-20: 88
- 2026-09-19: 88
- 2026-09-18: 88
- 2026-09-17: 88
- 2026-09-16: 87
- 2026-09-15: 87
- 2026-09-14: 87
- 2026-09-13: 86
- 2026-09-12: 86
- 2026-09-11: 85
- 2026-09-10: 85
- 2026-09-09: 84
- 2026-09-08: 84
- 2026-09-07: 83
- 2026-09-06: 83
- 2026-09-05: 82
- 2026-09-04: 82
- 2026-09-03: 81
- 2026-09-02: 81
- 2026-09-01: 80
- 2026-08-31: 80
- 2026-08-30: 80
- 2026-08-29: 79
- 2026-08-28: 79
- 2026-08-27: 78
- 2026-08-26: 78
- 2026-08-25: 76
- 2026-08-24: 76
- 2026-08-23: 75

## Common questions

### 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.

## Links

- Remote endpoint: https://ridedesk.app/api/mcp
- Repository: https://github.com/ridedeskapp/ridedesk
- Website: https://ridedesk.app/developers
- Changelog RSS feed: https://verifymcp.io/servers/app-ridedesk-docs/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/app-ridedesk-docs/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/app-ridedesk-docs/api-mcp