General Tools
ried.taxi
An MCP server for RIED taxi booking that provides fare quotes, availability checks, temporary holds, confirmed bookings, and booking status retrieval.
ENDPOINT 1
https://ried.taxi/api/mcp
MCP server metadata
- Name
- ried-taxi
- Version
- 2.0.0
RIED.TAXI: pre-booked private airport and long-distance transfers in one Tesla Model X (max 5 passengers) driven by the owner, Ronald. Based near Ried im Innkreis, Upper Austria. Main routes: Innviertel, Salzburg, Linz, Wels <-> Munich Airport, Salzburg Airport, Linz, Vienna. Not a local town taxi. Timezone Europe/Vienna for every date and time. Required flow for a booking - never skip or reorder: 1. Collect pickup address, destination, date, pickup time and passengers. 2. ried_taxi_get_quote. Only ever state the price it returns. Never use a remembered or calculated price. If status is manual_quote_required or not_offered, say so and give the WhatsApp contact; do not book. 3. ried_taxi_check_availability. If unavailable, offer the alternatives. 4. ried_taxi_hold_booking to hold the day (15 min) while you collect the rest: first and last name, mobile phone (international format), email (recommended), large suitcases, pickup instructions. Flight number and landing time ONLY when the pickup is at an airport (see flight_number_required in the quote). For trips without an airport never ask for a flight number. 5. Show the customer the complete booking (route as resolved by the quote, date, pickup time, passengers, luggage, flight, name, phone, price) and ask: "Shall I book this?" Also tell them their details go to RIED.TAXI to carry out the ride (privacy: https://ried.taxi/en/privacy/, terms: https://ried.taxi/en/terms/), that cancellation is free of charge, and ask whether RIED.TAXI may contact them on WhatsApp. 6. Only after an explicit yes: ried_taxi_create_booking with customer_confirmed=true, accepted_terms=true and a fresh idempotency_key. Reuse the SAME idempotency_key if you retry that same booking. 7. Give the customer the booking reference AND the access code. Both are needed to view, change or cancel later. A price question alone must never lead to a booking. Maximum 5 passengers. No roof box or trailer. Stops and child seats: manual quote via WhatsApp +43 7754 8009. Changes and cancellations: always preview/confirm with the customer first.
Known tools 7
ried_taxi_hold_bookingTemporarily reserves the quoted date for THIS customer for 15 minutes so nobody else (website or another assistant) can take it while the customer confirms.
Inferred read-onlyried_taxi_get_bookingReturns status, pickup time, addresses, price and flight of ONE booking.
Inferred read-onlyried_taxi_cancel_bookingCancels a booking, free of charge, any time before the pickup.
Potential side effectsCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.ried-taxi]
url = "https://ried.taxi/api/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"ried-taxi": {
"type": "http",
"url": "https://ried.taxi/api/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: ried-taxi
Remote MCP URL: https://ried.taxi/api/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"ried-taxi": {
"url": "https://ried.taxi/api/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"ried-taxi": {
"type": "http",
"url": "https://ried.taxi/api/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "ried-taxi",
"transport": "streamable-http",
"url": "https://ried.taxi/api/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.