_ registry / mcp streamable-http · checked 2h ago

RideDesk developer docs

https://ridedesk.app

Registry code: 1f38bda3380e92aa

api record

Documentation server for building on RideDesk (booking & dispatch SaaS for transfer and rental operators). This platform server is read-only and auth-free. Each operator ACCOUNT has its own authenticated BOOKING MCP server at https://<their-domain>/api/mcp — see the "mcp-connector" doc. Flow: list_docs → get_doc (pass the operator's domain as `host` to get examples pointed at the right account), or search_docs for a keyword. get_integration_brief returns a self-contained brief for building a booking website.

endpoint
https://ridedesk.app/api/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is RideDesk developer docs live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is RideDesk developer docs free to use?
Yes — the hub reached it with no key and no payment.
What tools does RideDesk developer docs have?
5 tools: get_doc, get_integration_brief, get_widget_snippets, search_docs, list_docs.
Is RideDesk developer docs safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 99.8%· all time 99.8%

latency
259ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 544 checks · signed record
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
topic
knowledge & reference documentation & docs search
used for
  • read booking platform developer documentation
  • search documentation by keyword
  • get widget snippets for a booking site
  • get an integration brief for a coding agent
takes → gives
text → text, code
tools
5 reads
note
documentation mirror
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 5 tools
4 open 1 never probed 4 of 5 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_integration_brief reads open 19h ago

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "host": {
      "type": "string",
      "description": "The operator's RideDesk domain (e.g. their-workspace.ridedesk.app or a custom domain). Optional — examples use a placeholder without it."
    }
  },
  "additionalProperties": false
}
    arguments 10 lines
  • get_widget_snippets reads open 19h ago

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

    mcp-tool

    {
  "type": "object",
  "properties": {
    "host": {
      "type": "string",
      "description": "The operator's RideDesk domain (e.g. their-workspace.ridedesk.app or a custom domain). Optional — examples use a placeholder without it."
    }
  },
  "additionalProperties": false
}
    arguments 10 lines
  • search_docs reads open 11h ago

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

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "host": {
      "type": "string",
      "description": "The operator's RideDesk domain (e.g. their-workspace.ridedesk.app or a custom domain). Optional — examples use a placeholder without it."
    },
    "query": {
      "type": "string",
      "description": "Keywords, an endpoint path, or a field name (e.g. \"quote_ref\", \"apple pay\", \"/api/enquiries\")"
    }
  },
  "additionalProperties": false
}
    arguments 17 lines
  • list_docs reads open 11h ago

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

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • get_doc reads unknown 19h ago

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

    mcp-tool

    {
  "type": "object",
  "required": [
    "topic"
  ],
  "properties": {
    "host": {
      "type": "string",
      "description": "The operator's RideDesk domain (e.g. their-workspace.ridedesk.app or a custom domain). Optional — examples use a placeholder without it."
    },
    "topic": {
      "enum": [
        "overview",
        "quote-and-book",
        "checkout",
        "endpoints",
        "widgets",
        "attribution",
        "live-chat",
        "customer-portal",
        "mcp-connector"
      ],
      "type": "string",
      "description": "A topic from list_docs"
    }
  },
  "additionalProperties": false
}
    arguments 28 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 1f38bda3380e92aa.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/1f38bda3380e92aa/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/1f38bda3380e92aa/badge.svg)](https://brick.blue/agent/1f38bda3380e92aa?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
90%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.