Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

RIED.TAXI

REMOTE · RIED.TAXI · SCANNED SEP 29

Fixed-price airport transfers and long rides from Upper Austria, Salzburg, Passau

Available components

+3 this week 64 Trust /100
Trust breakdown (7 categories)

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 Security63
Transport & Reachability100
Schema Quality & AI Usability57
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1909 tokens (~272/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
  • Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage87
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 54% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% 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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Install

How do I install the RIED.TAXI MCP server?

RIED.TAXI is a hosted endpoint at https://ried.taxi/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 · ried.taxi

# add to Claude Code
claude mcp add --transport http taxi-ried-booking 'https://ried.taxi/api/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "taxi-ried-booking": {
      "url": "https://ried.taxi/api/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "taxi-ried-booking": {
      "type": "http",
      "url": "https://ried.taxi/api/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.taxi-ried-booking]
url = "https://ried.taxi/api/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "taxi-ried-booking": {
      "type": "remote",
      "url": "https://ried.taxi/api/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add taxi-ried-booking --url 'https://ried.taxi/api/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  taxi-ried-booking:
    url: "https://ried.taxi/api/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "taxi-ried-booking": {
      "Transport": "http",
      "Url": "https://ried.taxi/api/mcp"
    }
  }
}
# add to Vellum
assistant mcp add taxi-ried-booking -t streamable-http -u 'https://ried.taxi/api/mcp'
// mcp.json
{
  "mcpServers": {
    "taxi-ried-booking": {
      "type": "http",
      "url": "https://ried.taxi/api/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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.

  • 28 Sept 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 24 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 23 Sept 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 22 Sept 26 61

    First indexed and scored.

Diagnostics

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 29 Sept 2026 · Probed https://ried.taxi/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=ried.taxi CN=WE1,O=Google Trust Services,C=US 24 Sept 2026 23 Dec 2026 ECDSA 256 ECDSA-SHA256 47776672e3011bb71301f8863512b004
SANs: ried.taxi, *.ried.taxi
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 ried.taxi. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
taxi. present 28756 8 Verified
ried.taxi. 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=31536000; includeSubDomains
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://ried.taxi/api/mcp Verified 200
http (plaintext) http://ried.taxi/api/mcp HTTPS enforced 301 https://ried.taxi/api/mcp
MCP tools · 7 exposed · ~1,386 tokens

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 →

Tool Tokens
ried_taxi_cancel_booking ~134

Cancels a booking, free of charge, any time before the pickup. Requires reference, access code, customer_confirmed=true after the customer explicitly confirmed, and an idempotency_key. Cannot be undone.

NameTypeReqDescription
access_codestringyes8-character access code given at booking time.
booking_referencestringyesPublic booking reference, e.g. RT-K7QM.
customer_confirmedbooleanyes–
idempotency_keystringyesUnique key for this one intended action. Reuse it only when retrying the same action.
reasonstring––
NameTypeReqDescription
booking_idstring––
booking_referencestring––
cancellation_fee_eurnumber––
cancelled_atstring––
confirmation_urlstring|null––
currencystring––
destinationstring––
errorstring––
flight_numberstring|null––
free_cancellation_untilstring––
messagestring––
okbooleanyes–
passengersinteger|null––
pickup_addressstring––
pickup_atstring––
pickup_datestring––
pickup_timestring––
price_eurnumber|null––
statusstring––
timezonestring––

No examples provided.

ried_taxi_check_availability ~135

Checks RIED.TAXI's real calendar (bookings, the owner's own calendar and other customers' temporary holds). One car, one driver: availability depends on the whole day including driving to the pickup and back, not only the minute. Read-only; a free result is NOT a reservation. Returns alternatives when unavailable.

NameTypeReqDescription
destination_addressstring––
passengersinteger––
pickup_addressstring––
pickup_datestringyesYYYY-MM-DD (Europe/Vienna).
pickup_timestringyesHH:MM, 24h, Europe/Vienna.
NameTypeReqDescription
alternative_datesarray––
alternative_timesarray––
availability_refstring––
availableboolean––
errorstring––
messagestring––
okbooleanyes–
pickup_atstring––
reasonstring––
timezonestring––

No examples provided.

ried_taxi_create_booking ~504

Creates a REAL, CONFIRMED booking in RIED.TAXI's booking system and blocks the day. Only call after the customer has seen the complete trip and price and explicitly said yes. Requires the quote_id, customer_confirmed=true, accepted_terms=true and an idempotency_key (retrying with the same key never creates a second booking). Returns the booking reference and an access code for the customer.

NameTypeReqDescription
accepted_termsbooleanyesCustomer accepted that RIED.TAXI processes their details to carry out the ride (https://ried.taxi/en/privacy/) and the booking terms (https://ried.taxi/en/terms/; cancellation is free of charge).
child_seatsstring–Not bookable online; must be empty.
customer_confirmedbooleanyesCustomer saw the full booking summary and explicitly said to book it.
destination_addressstringyes–
emailstring––
first_namestringyes–
flight_arrival_timestring–Scheduled landing time (local) - required for airport pickups.
flight_departure_timestring–Scheduled departure time for rides TO the airport (optional).
flight_numberstring–Required when picking up at an airport.
hand_luggageinteger––
hold_idstring––
idempotency_keystringyesUnique key for this one intended action. Reuse it only when retrying the same action.
languagestringyes–
large_suitcasesintegeryes–
last_namestringyes–
notesstring––
passengersintegeryes–
phonestringyesMobile number in international format, e.g. +43 660 1234567.
pickup_addressstringyesExact pickup address (street + number + town, hotel, or airport + terminal).
pickup_datestringyesYYYY-MM-DD (Europe/Vienna).
pickup_instructionsstring––
pickup_timestringyesRequested DRIVER PICKUP time, HH:MM Europe/Vienna. For an airport arrival this is normally the scheduled landing time; the driver monitors the flight.
quote_idstringyes–
stopsarray–Not bookable online; must be empty.
whatsapp_opt_inbooleanyesTrue only if the customer agreed to WhatsApp messages about this ride.
NameTypeReqDescription
access_codestring––
booking_idstring––
booking_referencestring––
confirmation_urlstring|null––
currencystring––
destinationstring––
errorstring––
flight_numberstring|null––
free_cancellation_untilstring––
messagestring––
okbooleanyes–
passengersinteger|null––
pickup_addressstring––
pickup_atstring––
pickup_datestring––
pickup_timestring––
price_eurnumber|null––
replayedboolean––
statusstring––
timezonestring––

No examples provided.

ried_taxi_get_booking ~80

Returns status, pickup time, addresses, price and flight of ONE booking. Requires the booking reference and the access code the customer received when booking. Read-only.

NameTypeReqDescription
access_codestringyes8-character access code given at booking time.
booking_referencestringyesPublic booking reference, e.g. RT-K7QM.
NameTypeReqDescription
booking_idstring––
booking_referencestring––
confirmation_urlstring|null––
currencystring––
destinationstring––
errorstring––
flight_numberstring|null––
free_cancellation_untilstring––
messagestring––
okbooleanyes–
passengersinteger|null––
pickup_addressstring––
pickup_atstring––
pickup_datestring––
pickup_timestring––
price_eurnumber|null––
statusstring––
timezonestring––

No examples provided.

ried_taxi_get_quote ~249

Returns RIED.TAXI's current price for one journey, calculated by the ried.taxi backend (the only valid price source). Read-only: it never books or reserves anything. Returns quote_id (valid 30 min), status priced | manual_quote_required | not_offered, and the resolved pickup/destination - show those names to the customer. If the result is ambiguous_place, ask the customer which place they mean and resend with the postcode.

NameTypeReqDescription
child_seatsstring–Ages of children needing a seat. Means manual_quote_required.
destination_addressstringyes–
flight_numberstring––
large_suitcasesinteger––
passengersintegeryes–
pickup_addressstringyesStreet address, hotel, town with postcode, or airport name/code (MUC, SZG, LNZ, VIE).
pickup_datestring–YYYY-MM-DD (Europe/Vienna).
pickup_timestring–HH:MM, 24h, Europe/Vienna.
special_requirementsstring––
stopsarray–Intermediate stops. Any stop means manual_quote_required.
NameTypeReqDescription
candidatesarray––
currencystring––
destination_resolvedobject––
errorstring––
includedarray––
messagestring––
okbooleanyes–
pickup_resolvedobject––
price_eurnumber|null––
price_typestring|null––
promotionnull––
quote_idstring|null––
statusstring––
valid_untilstring––
waiting_rulesstring––

No examples provided.

ried_taxi_hold_booking ~104

Temporarily reserves the quoted date for THIS customer for 15 minutes so nobody else (website or another assistant) can take it while the customer confirms. Expires automatically. Not a booking. Call after availability is confirmed and the customer wants to proceed.

NameTypeReqDescription
pickup_datestringyesYYYY-MM-DD (Europe/Vienna).
pickup_timestringyesHH:MM, 24h, Europe/Vienna.
quote_idstringyes–
NameTypeReqDescription
errorstring––
expires_atstring––
expires_in_minutesinteger––
hold_idstring––
messagestring––
okbooleanyes–
pickup_datestring––

No examples provided.

ried_taxi_update_booking ~180

Changes a booking. Always call first with mode='preview' and show the result to the customer; then call with mode='apply', customer_confirmed=true and an idempotency_key. Same-day time changes, flight number, passengers (max 5), notes and new addresses with the same price apply immediately; a new date or a different price is sent to Ronald for approval (status change_requested).

NameTypeReqDescription
access_codestringyes8-character access code given at booking time.
booking_referencestringyesPublic booking reference, e.g. RT-K7QM.
changesobjectyes–
customer_confirmedboolean––
idempotency_keystring–Unique key for this one intended action. Reuse it only when retrying the same action.
modestringyes–
NameTypeReqDescription
booking_idstring––
booking_referencestring––
changesobject––
confirmation_urlstring|null––
currencystring––
destinationstring––
errorstring––
flight_numberstring|null––
free_cancellation_untilstring––
handledstring––
messagestring––
okbooleanyes–
passengersinteger|null––
pickup_addressstring––
pickup_atstring––
pickup_datestring––
pickup_timestring––
price_eurnumber|null––
statusstring––
timezonestring––
updated_fieldsarray––

No examples provided.

Common questions

What is the RIED.TAXI MCP server?

RIED.TAXI is an MCP server listed in the public MCP registry as taxi.ried/booking. Fixed-price airport transfers and long rides from Upper Austria, Salzburg, Passau. This page covers its hosted endpoint (https://ried.taxi/api/mcp).

Is the RIED.TAXI MCP server safe to use?

RIED.TAXI scores 64 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 RIED.TAXI MCP server expose?

RIED.TAXI exposes 7 tools: ried_taxi_get_quote, ried_taxi_check_availability, ried_taxi_hold_booking, ried_taxi_create_booking, ried_taxi_get_booking, and 2 more. Their descriptions and schemas cost roughly 1,386 tokens of context every time the server is loaded.

Does the RIED.TAXI MCP server require authentication?

No. We connected to RIED.TAXI without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the RIED.TAXI MCP server still maintained?

RIED.TAXI is still listed as active in the MCP registry. We last reached this channel on 29 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.