Aurinia — book across venues via your AI assistant
Server Details
Find availability and book across a network of independent venues via your AI assistant.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-06-18
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 8 tools
Each tool maps to a distinct step in the venue-booking lifecycle: discovery (find_providers), detail (get_provider_info), pricing/slots (get_availability), and the booking actions. The only real overlap is book vs reschedule, which the descriptions explicitly delimit (same-day doctor moves go to reschedule, cross-day and hostel changes go to book). find_providers vs get_provider_info is a mild search-vs-fetch ambiguity but is clarified by parameter shape (query vs provider_id).
Five tools follow a clean verb_noun pattern (find_providers, get_availability, get_provider_info, list_current_bookings, list_past_bookings). The remaining three (book, cancel, reschedule) are bare verbs rather than e.g. create_booking/cancel_booking, a minor but readable deviation. No camelCase/snake_case mixing at the tool-name level.
Eight tools is well within the ideal 3-15 range and each earns its place: two are discovery/read tools, two are listing tools, and four cover the booking lifecycle. There is no filler or redundant endpoint for what is a fairly narrow domain (book across venues).
The core lifecycle is covered end to end: find venue, inspect it, check availability, book, cancel, reschedule, and list current/past bookings, including partial coverage of consent/payment hand-offs via returned URLs. Gaps are modest: there is no tool to query or revoke authorization status across venues, no payment-finalization tool (hostel holds depend on an external payment_url), and no hostel reschedule (documented workaround: cancel + book).
Available Tools
8 toolsbookAInspect
Books at a network venue on the user's behalf. Takes provider_id and item, which the venue interprets: doctor — item={date,time}; hostel — item={check_in,check_out,guests,promo_code?} (underscores: check_in/check_out, not 'checkin'/'checkout'; guests is an integer; a dorm bed is the default, there is no room_type). No name or contact is required: identity comes from the one-time Telegram consent. At a hostel the call returns a HOLD together with a payment_url, and the booking is finalized by payment rather than by this call; a doctor visit is free. If the user is not yet authorized at that venue the call returns linked=false with consent_url (and consent_url_native when available) instead of a booking, and the same call succeeds once the user has approved in Telegram. Authorization: one Telegram consent per venue, which also covers later calls.
Inputs: item (required), provider_id (required).
cancelAIdempotentInspect
Cancels a booking at a network venue. Takes provider_id and item={booking_id}, where booking_id comes from list_current_bookings. A cancellation is reversible — the freed slot or bed can be booked again — which is why this tool is not marked destructive. If the user is not yet authorized at that venue the call returns a consent link instead. Authorization: one Telegram consent per venue, which also covers later calls.
Inputs: item (required), provider_id (required).
find_providersARead-onlyInspect
Find a venue in the Aurinia network. Venue types currently bookable: doctor, hostel. Optional: query (e.g. 'vertebrologist'), city, type. Returns a providers array; use a provider_id from it for get_availability / book.
Inputs: city, type, query. Returns: providers
get_availabilityARead-onlyInspect
Availability and price at a venue. provider_id is required. Parameter names are venue-specific: doctor — date (YYYY-MM-DD); hostel — check_in, check_out, guests (with underscores: check_in/check_out, not 'checkin'/'checkout'; guests is an integer). There is no room_type parameter — a dorm bed is the default. Optional promo_code applies an AI-booking discount. A null availability usually means either nothing free or mistyped parameter names, check_in/check_out being the common slip.
Inputs: provider_id (required), date, guests, check_in, +2 more. Returns: provider, availability
get_provider_infoARead-onlyInspect
Details for one venue by provider_id: id, type (doctor/hostel), name, city, address. Read-only, no auth. Use it to confirm a venue before get_availability / book.
Inputs: provider_id (required). Returns: id, city, name, type, +1 more
list_current_bookingsARead-onlyInspect
The user's current/upcoming bookings at a network venue (by date, nearest first). Each has a status field (e.g. booked/confirmed/cancelled) — distinguish active vs cancelled. provider_id optional (without it — the first venue). Requires authorization.
Inputs: provider_id.
list_past_bookingsARead-onlyInspect
The user's past bookings at a network venue (by date, most recent first). Each has a status field. provider_id optional; limit (default 20)/offset for pagination. Requires authorization.
Inputs: limit, offset, provider_id.
rescheduleAIdempotentInspect
Moves an existing booking at a network venue. Takes provider_id and item; for a doctor that is {date, from, to}, and the move is atomic within the same day — if the target slot is taken in the race, the user keeps the slot they already held, so either outcome leaves them with a booking. A move to a different day is a fresh booking, so book is the right call for that. Support varies by venue: a hostel has no reschedule, where a cancel followed by a new book is the equivalent. If the user is not yet authorized at that venue the call returns a consent link instead. Authorization: one Telegram consent per venue, which also covers later calls.
Inputs: item (required), provider_id (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Last-minute booking slots across 11 suppliers. Search, price, and execute bookings via AI agents.
Find local businesses, read services and times, ask their AI receptionist, send booking requests.
Discover and book businesses via AI agents.
Find free times at Gaplessly businesses on a plan with AI booking, then get a link to book.
Related MCP Servers
- AlicenseAqualityBmaintenanceBook a table, an appointment or a place in a class at a real local business. Live availability, instant confirmation, no account and no API key. Eight tools: search, fetch, get_business, check_availability, create_booking, check_booking, cancel_booking and request_listing. Guest emails in eight languages. Hosted at https://g-guest.app/api/mcp818 npmMIT
- FlicenseNot gradedqualityBmaintenanceEnables customers and AI agents to check restaurant table availability and create bookings, returning confirmations or nearby alternative times when a slot is full, with atomic capacity control and idempotent handling.-
- AlicenseNot gradedqualityBmaintenanceEnables small local businesses to offer Alexa+ voice booking from one self-hosted, multi-business deployment with strict per-business isolation. It supports finding businesses, searching slots, two-step booking, rescheduling and cancellation with deposits, cross-session memory, bookings for people you care for, agentic waitlist recovery, notifications, and an owner dashboard.MIT
- AlicenseNot gradedqualityCmaintenanceLuxury hotel intelligence and secure checkout handoff for AI travel agents.1Apache 2.0
Glama MCP Gateway
Add one secure layer between your agents and this server.