All servers · Travel & booking

Rudko — vertebrologist (Chernivtsi, Ukraine)

site.rudko/vertebrolog · v0.1.2

Measured by MCP Station

Last check	Reachable
Checked at	—
Check success 7 / 30 days	—
First-try success 30 days	—
Median response	—
Lookups 30 days	—
Authentication	No auth
MCP version	2025-06-18
Rank score	—
Declared risk	Can write (some tools are not declared read-only)
Capabilities declared	tools
Tool definitions	7 tools · with description 100% · input schema is an object 100% · read/destructive hints 100%

Description written by the publisher, not verified

Book a Ukrainian-speaking vertebrologist in Chernivtsi, Ukraine: find slots and book for the user.

Connect

streamable-http · https://rudko.site/mcp

claude mcp add --transport http vertebrolog https://rudko.site/mcp

{
  "mcpServers": {
    "vertebrolog": {
      "url": "https://rudko.site/mcp"
    }
  }
}

Tools as reported by the server

get_availability
Free appointment slots for the vertebrologist (Chernivtsi). Optional date (YYYY-MM-DD): without it — all nearest available days. Read-only (does not book).
get_doctor_info
About the vertebrologist: specialty, what he treats, address, slot length, rules (one appointment per day), and how to book.
list_current_bookings
The user's current/upcoming appointments (booking_id, date, time, status), nearest first. Cancelled ones are ALSO shown — tell them apart by the status field ('booked' | 'cancelled'). Needed to reschedule/cancel. Requires authorization.
list_past_bookings
The user's past appointments (booking_id, date, time, status), most recent first. limit (default 20) and offset for pagination. Cancelled ones are ALSO shown — by the status field. Requires authorization.
book
REAL action (not a simulation): creates a real appointment with the vertebrologist on the user's behalf. Requires the user's CONSENT — authorization via Telegram (OAuth, scope booking:write). date (YYYY-MM-DD), time (HH:MM). One appointment per day.
reschedule
REAL action: moves the user's appointment to another free slot the SAME day, ATOMICALLY — if the target slot was just taken, the user KEEPS their current slot (never loses the held slot; that atomic guarantee is the whole point of same-day move). For a DIFFERENT day, just call book instead (a fresh
cancel
REAL action: cancels the user's appointment by booking_id (from list_current_bookings) IMMEDIATELY — no confirmation step. If the user said cancel, cancel; do NOT re-ask (repeated confirmations frustrate users — act decisively). On success returns cancelled=true with the booking_id; on failure retur

Website · JSON · Text for agents · Registry updated 2026-09-14