RIED.TAXI MCP server
taxi.ried/bookingried.taxistreamable-httpv1.0.0Scanned
Fixed-price airport transfers and long rides from Upper Austria, Salzburg, Passau
7 tools: 2 can delete or cancel things, 3 change things and 2 only read.
- Reads private data · 0
- Reads text others write · 3
- Can send data out · 1
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
2 tools here can delete or cancel things. Govern them.
- 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 RIED.TAXI MCP server can do
The RIED.TAXI MCP server is published by ried.taxi, a domain the MCP Registry verified. It has 7 tools. It can delete or cancel things (2 tools: ried_taxi_update_booking and ried_taxi_cancel_booking) and create or change data (3 tools: ried_taxi_check_availability, ried_taxi_recheck_availability and ried_taxi_create_booking). 2 tools only read.
3 tools bring in text other people can write (ried_taxi_create_booking, ried_taxi_update_booking and ried_taxi_cancel_booking); 1 tool can send data out of your system (ried_taxi_create_booking).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 19, 2026, version 1.0.0.
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.
7 tools
Deletes or cancels 2Claude Code: deny
ried_taxi_cancel_bookingCancels a booking, free of charge, any time before the pickup.Reads text others writeNo findings
Why it is in this group
- The name "ried_taxi_cancel_booking" says "cancel": a word for removing or ending something.
- The description says "Cannot be undone".
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: Cancel my RIED.TAXI booking
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: true
ried_taxi_update_bookingChanges a booking.Reads text others writeNo findings
Why it is in this group
- The name "ried_taxi_update_booking" says "update": a word for a change.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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).
Annotations the server declares
- title: Change my RIED.TAXI booking
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: true
Changes things 3Claude Code: ask
ried_taxi_check_availabilityChecks RIED.TAXI's real calendar (bookings, the owner's own calendar and other customers' temporary holds).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- title: Check RIED.TAXI availability
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
ried_taxi_create_bookingCreates a REAL, CONFIRMED booking in RIED.TAXI's booking system and blocks the day.Reads text others writeCan send data outNo findings
Why it is in this group
- The name "ried_taxi_create_booking" says "create": a word for a change.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe input takes a destination (input.phone): what the tool writes goes there.
Description, as the server wrote it 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.
Annotations the server declares
- title: Create a confirmed RIED.TAXI booking
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
ried_taxi_recheck_availabilityRe-checks that the quoted date is still free right before the booking.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Re-checks that the quoted date is still free right before the booking. It does NOT block or reserve the day - RIED.TAXI only blocks a day with a created booking. Returns available=true/false (with alternative dates) and held=false. Call it when the customer wants to proceed, then show the summary and create the booking right after their explicit yes.
Annotations the server declares
- title: Re-check the day before booking
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Only reads 2Show 2 read-only tools
ried_taxi_get_bookingReturns status, pickup time, addresses, price and flight of ONE booking.No findings
Why it is in this group
- The name "ried_taxi_get_booking" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Look up my RIED.TAXI booking
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
ried_taxi_get_quoteReturns RIED.TAXI's current price for one journey, calculated by the ried.taxi backend (the only valid price source).No findings
Why it is in this group
- The name "ried_taxi_get_quote" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Get live RIED.TAXI price
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- 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 private-data.
- Reads private data0
- 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 out1
- 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, 19:19 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
- 5
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://ried.taxi/.well-known/oauth-protected-resource
- Authorization servers
- https://ried.taxi/dispatch
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- yes
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 5 tools that change things (2 destructive, 3 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://ried.taxi/api/mcp: tools/list returned 7 tools to an anonymous client, including ried_taxi_update_booking (destructive), ried_taxi_cancel_booking (destructive), ried_taxi_check_availability (write), ried_taxi_recheck_availability (write), ried_taxi_create_booking (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
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.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http booking https://ried.taxi/api/mcpclaude mcp add --transport http booking https://ried.taxi/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__booking__ried_taxi_get_quote",
"mcp__booking__ried_taxi_get_booking"
],
"ask": [
"mcp__booking__ried_taxi_check_availability",
"mcp__booking__ried_taxi_recheck_availability",
"mcp__booking__ried_taxi_create_booking"
],
"deny": [
"mcp__booking__ried_taxi_update_booking",
"mcp__booking__ried_taxi_cancel_booking"
]
}
}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 booking. Review it before you use it.
Capability tags behind 3 rules
- mcp__booking__ried_taxi_create_booking untrusted-input, outbound
- mcp__booking__ried_taxi_update_booking untrusted-input
- mcp__booking__ried_taxi_cancel_booking 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/taxi.ried/booking/verify?hash=ff618aae9bfd37e3d8a7d2dd92c2c8360bb75b05fef047bec67ba0b641acf260" | jq -e '.changed == false'Pinned hash ff618aae9bfd, from Nov 19, 2026, 06:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/taxi.ried/booking/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/taxi.ried/booking)Source: MCP Registry. Synced Oct 21, 2026, 18:55 UTC.
RIED.TAXI MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the RIED.TAXI MCP server safe?
- No scan can promise that. What its definitions show: 7 tools, 5 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the RIED.TAXI MCP server delete data?
- Yes. 2 tools can delete, cancel or revoke something: ried_taxi_update_booking and ried_taxi_cancel_booking.
Can the RIED.TAXI 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 RIED.TAXI MCP server have?
- 7 tools: 2 destructive, 3 write, 2 read. ried_taxi_update_booking, ried_taxi_cancel_booking, ried_taxi_check_availability, ried_taxi_recheck_availability, ried_taxi_create_booking, ried_taxi_get_quote and ried_taxi_get_booking.
Does the RIED.TAXI MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the RIED.TAXI MCP server send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): ried_taxi_create_booking.
Has the RIED.TAXI MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 19, 2026.