RideDesk Developer Docs MCP server
app.ridedesk/docsridedesk.appstreamable-httpv1.0.3Scanned
Developer docs for building on RideDesk: booking API, widgets, per-account booking MCP. No auth.
5 tools: 1 change things and 4 only read.
- Reads private data · 4
- Reads text others write · 3
- Can send data out · 0
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here changes things. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the RideDesk Developer Docs MCP server can do
The RideDesk Developer Docs MCP server is published by ridedesk.app, a domain the MCP Registry verified. It has 5 tools. It can create or change data (1 tool: get_widget_snippets), but cannot delete data. 4 tools only read.
4 tools read private data (list_docs, get_doc, search_docs and 1 more); 3 tools bring in text other people can write (get_doc, get_integration_brief and get_widget_snippets).
The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 10, 2026, version 1.0.3.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
5 tools
Changes things 1Claude Code: ask
get_widget_snippetsCopy-paste tags: the attribution script, the live-chat script, and the embeddable booking/enquiry/rental widget iframes.Reads private dataReads text others write1 finding
Why it is in this group
- The name "get_widget_snippets" says "get": a word for reading.
- The description's first verb is "copy": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- private-dataThe description's first sentence says "chat": it reads messages.
- untrusted-inputThe description's first sentence says "copy" and "chat": it reads messages, which other people can write.
Findings
- Warn
The server marks "get_widget_snippets" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The name "get_widget_snippets" says "get": a word for reading.
Description, as the server wrote it Copy-paste tags: the attribution script, the live-chat script, and the embeddable booking/enquiry/rental widget iframes.
Annotations the server declares
- title: Get widget & tag snippets
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
Only reads 4Show 4 read-only tools
get_docOne documentation topic as markdown: the booking API contract, checkout, widgets, attribution, live chat, the customer portal, or the per-account booking MCP server.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "get_doc" says "get": a word for reading.
What it can reach
- private-dataThe name "get_doc" says "get" and "doc": it reads documents.
- private-dataThe description's first sentence says "chat": it reads messages.
- untrusted-inputThe description's first sentence says "chat": it reads messages, which other people can write.
Description, as the server wrote it One documentation topic as markdown: the booking API contract, checkout, widgets, attribution, live chat, the customer portal, or the per-account booking MCP server.
Annotations the server declares
- title: Read a documentation topic
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
get_integration_briefA 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.Reads text others writeNo findings
Why it is in this group
- The name "get_integration_brief" says "get": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "website": it reads web pages, which anyone can write.
Description, as the server wrote it 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.
Annotations the server declares
- title: Get the integration brief
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
list_docsThe available documentation topics with one-line summaries.Reads private dataNo findings
Why it is in this group
- The name "list_docs" says "list": a word for reading.
What it can reach
- private-dataThe name "list_docs" says "list" and "doc": it reads documents.
Description, as the server wrote it The available documentation topics with one-line summaries. Call first, then get_doc.
Annotations the server declares
- title: List documentation topics
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
search_docsKeyword search across all documentation topics.Reads private dataNo findings
Why it is in this group
- The name "search_docs" says "search": a word for reading.
What it can reach
- private-dataThe name "search_docs" says "search" and "doc": it reads documents.
Description, as the server wrote it Keyword search across all documentation topics. Returns matching sections with excerpts; follow up with get_doc for the full topic.
Annotations the server declares
- title: Search the documentation
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.
- Reads private data4
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write3
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:30 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 1
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://ridedesk.app/.well-known/oauth-protected-resource/api/mcp
- Authorization servers
- https://ridedesk.app
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- yes
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://ridedesk.app/api/mcp: tools/list returned 5 tools to an anonymous client, including get_widget_snippets (write)
Findings
Matches of fixed checks, with the text they matched.
The server marks "get_widget_snippets" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The name "get_widget_snippets" says "get": a word for reading.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.3. Values in angle brackets are yours to fill in.
claude mcp add --transport http docs https://ridedesk.app/api/mcpclaude mcp add --transport http docs https://ridedesk.app/api/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__docs__list_docs",
"mcp__docs__get_doc",
"mcp__docs__search_docs",
"mcp__docs__get_integration_brief"
],
"ask": [
"mcp__docs__get_widget_snippets"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as docs. Review it before you use it.
Capability tags behind 5 rules
- mcp__docs__list_docs private-data
- mcp__docs__get_doc private-data, untrusted-input
- mcp__docs__search_docs private-data
- mcp__docs__get_integration_brief untrusted-input
- mcp__docs__get_widget_snippets private-data, untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/app.ridedesk/docs/verify?hash=72b58008724790d4020e89194a87e784c750c36a4d0b0c6dbcd6a0155d3b668a" | jq -e '.changed == false'Pinned hash 72b580087247, from Nov 10, 2026, 06:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/app.ridedesk/docs/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/app.ridedesk/docs)Source: MCP Registry · repository. Synced Oct 21, 2026, 17:44 UTC.
RideDesk Developer Docs MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the RideDesk Developer Docs MCP server safe?
- No scan can promise that. What its definitions show: 5 tools, 1 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the RideDesk Developer Docs MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the RideDesk Developer Docs MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the RideDesk Developer Docs MCP server have?
- 5 tools: 1 write, 4 read. get_widget_snippets, list_docs, get_doc, search_docs and get_integration_brief.
Does the RideDesk Developer Docs MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the RideDesk Developer Docs MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the RideDesk Developer Docs MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 10, 2026.