Рудько — лікар-вертебролог

endpoint

https://rudko.site/mcp

door code

ebc8d9854ba8d958

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 Рудько — лікар-вертебролог live?

Yes — it answered the hub's last check (checked 53m ago). It answered 100% of checks over the last 30 days.

Is Рудько — лікар-вертебролог free to use?

Yes — the hub reached it with no key and no payment.

What tools does Рудько — лікар-вертебролог have?

7 tools: book, reschedule, cancel, list_current_bookings, list_past_bookings, get_doctor_info, get_availability.

Is Рудько — лікар-вертебролог 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.

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_doctor_info reads open 8h ago

  About the vertebrologist: specialty, what he treats, address, slot length, rules (one appointment per day), and how to book.

  mcp-tool

  1234

  {
    "type": "object",
    "properties": {}
  }

  arguments 4 lines copy
• get_availability reads open 8h ago

  Free appointment slots for the vertebrologist (Chernivtsi). Optional date (YYYY-MM-DD): without it — all nearest available days. Read-only (does not book).

  mcp-tool

  123456789

  {
    "type": "object",
    "properties": {
      "date": {
        "type": "string",
        "description": "YYYY-MM-DD (optional)"
      }
    }
  }

  arguments 9 lines copy
• book changes data unknown never probed

  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.

  mcp-tool

  123456789101112131415

  {
    "type": "object",
    "required": [
      "date",
      "time"
    ],
    "properties": {
      "date": {
        "type": "string"
      },
      "time": {
        "type": "string"
      }
    }
  }

  arguments 15 lines copy
• reschedule changes data unknown never probed

  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 booking; cross-day needs no atomic hold). No confirmation — act on request. Consent is a one-time Telegram OAuth (scope booking:write), already done — never re-prompt per action. date (YYYY-MM-DD), from (HH:MM current), to (HH:MM new).

  mcp-tool

  12345678910111213141516171819

  {
    "type": "object",
    "required": [
      "date",
      "from",
      "to"
    ],
    "properties": {
      "to": {
        "type": "string"
      },
      "date": {
        "type": "string"
      },
      "from": {
        "type": "string"
      }
    }
  }

  arguments 19 lines copy
• cancel changes data unknown never probed

  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 returns ok=false with a reason (not_found / bad_id). Consent is a one-time Telegram OAuth (scope booking:write), already done — never re-prompt per action. To change the time instead, prefer reschedule.

  mcp-tool

  1234567891011

  {
    "type": "object",
    "required": [
      "booking_id"
    ],
    "properties": {
      "booking_id": {
        "type": "string"
      }
    }
  }

  arguments 11 lines copy
• list_current_bookings reads unknown never probed

  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.

  mcp-tool

  1234

  {
    "type": "object",
    "properties": {}
  }

  arguments 4 lines copy
• list_past_bookings reads unknown never probed

  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.

  mcp-tool

  1234567891011

  {
    "type": "object",
    "properties": {
      "limit": {
        "type": "integer"
      },
      "offset": {
        "type": "integer"
      }
    }
  }

  arguments 11 lines copy

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

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.