mcpbeat Sign in

Loyalist Reservations MCP Server

by eatloyalist Your server? Claim it
answering

Loyalist Reservations is answering right now. Last checked 11 min ago. It exposes 5 tools.

Book tables at restaurants on the Loyalist network. No login; read availability, then book.

Uptime history 19 days of history
19 days agonow
100.0%
Uptime 24h
91 of 91 checks
5
Tools
read from the server
416 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 2

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 21 October 2026. No other catalogue keeps this.

28 Oct a tool changed version
21 Oct a tool description was rewritten find_venues

Nothing serious here today

Today is the operative word: we check Loyalist Reservations every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 11 min ago.

run in your terminal
claude mcp add restaurant-reservations --transport http https://agent.eatloyalist.com/mcp
Settings → Connectors → Add custom connector, then paste this address
https://agent.eatloyalist.com/mcp
~/.codex/config.toml
[mcp_servers.restaurant-reservations]
url = "https://agent.eatloyalist.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "restaurant-reservations": {
      "url": "https://agent.eatloyalist.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "restaurant-reservations": {
      "type": "http",
      "url": "https://agent.eatloyalist.com/mcp"
    }
  }
}

Available tools 5

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

availability
get_availability
Bookable times at one venue, on one date, for one party size. `date` is the venue's own local calendar date, `YYYY-MM-DD`. Each slot carries a `slot_id` to pass to book and a `starts_at` that is a full venue-local datetime, so a service running past midnight is unambiguous without you having to infer the day. An empty `slots` list means nothing is open on those terms, not that the venue is closed. Try a different time, party size or date before telling someone it is full.
book
book
Book a table. This takes a real table at a real restaurant. Pass a `slot_id` from get_availability. Confirm the venue, date, time and party size with the person before calling this, and do not call it speculatively: there is no cancel tool, so a booking made by mistake has to be undone by the guest phoning the restaurant. Calling it twice with identical arguments is safe and returns the same reservation rather than taking a second table. Changing the slot or the guest makes it a different booking, so re-read availability rather than editing the arguments to "retry". `phone` is optional here but required by some venues; omitting it can come back as `guest_field_required`. `note` reaches the restaurant as the reservation's note. `source` is where you found this venue: if the restaurant's own website told you a value to pass (in its markup or llms.txt), send it here so the restaurant can see its own site drove the booking. Leave it out if you did not arrive through one. `reservation_id` is for your own use, to read the booking back with get_reservation. It is not a confirmation number the venue knows, so do not read it out to the guest: tell them the restaurant, date, time and party size instead.
join
join_waitlist
Ask to be told if a table opens at a time the guest actually wants. This is not a reservation and never becomes one by itself. The venue contacts the guest if something frees up, so say that plainly rather than implying a table is held. Offer it whenever the guest cannot get a time that suits them, which is far more often than a venue being completely full: someone who wants 7:30 and is offered 5:00 or 9:45 may well prefer to wait for 7:30. An empty get_availability is only the most obvious case. Try other times, party sizes and dates first, then ask whether they would rather wait than take a time that does not work. Record what they wanted in `time_range`, not the time you found. `date` is the venue's own local calendar date, `YYYY-MM-DD`. `time_range` is required and is the window in the guest's words, like "7:00 PM - 9:00 PM" or "7:00 PM"; ask the guest for it rather than guessing, because the venue works the list by when people wanted to come. The email address is where the confirmation goes, so it must be the guest's own. Not every venue accepts these. One that does not refuses with a message saying so, which is an answer, not an error to retry. There is no reference number to give the guest, so the response is the only record either of you gets. Confirm it back to them by the restaurant, date and time. Mention the confirmation email only when `confirmation_sent` is true. When it is false the request is still on the venue's list, the note simply did not go out, so say they are on the list and that no email is coming rather than promising one.
reservation
get_reservation
Read one booking this credential made back from the venue. Use it to confirm a booking landed. A `status` of `pending` means the venue has not answered yet, not that it failed; treat anything you do not recognise as non-terminal rather than reporting a failure.
venues
find_venues
Restaurants bookable through this network, and what each one's system supports. Returns every venue that has opted in, across restaurant groups. Two optional filters narrow it, never widen it: `signup_form_id` to one website's venues when you found an Orion signup embed on a restaurant's page, and `venue_id` to a single venue when you already have its loyalist-venue-id (off a page's markup or a ReserveAction entry point) and want just that one rather than listing them all and matching yourself. Neither can reach a venue that has not opted in. A venue with `bookable: false` has no reservation system connected and will return no availability.

Endpoints

URLTransportStateLatencyChecked
https://agent.eatloyalist.com/mcp streamable-http answering 420 ms 11 min ago

Alternatives to Loyalist Reservations

same job, measured the same way
Dubai Table
by dubaitable

Book tables at Dubai's top restaurants, beach clubs and nights: live availability and prices.

13 tools answering
Easytable MCP
by chrischall

easyTable restaurant reservations for Claude — availability, and create/modify/cancel bookings

428 installs/wk local only
Discovery
by mizam

Find restaurants on Mizam: live menus, allergens, prices, hours, table availability. Read-only.

answering
GoTable MCP by usefulapi
by usefulapi

Read availability, reservations, guests; create, change, cancel bookings; add notes in GoTable.

21 tools answering
Dine MCP
by benjamin-di

Restaurant table availability across SevenRooms, TableCheck and ResDiary. Read-only; never books.

1 216 installs/wk local only
Citybikes MCP
by mrfentmen

List bike share networks and live station availability from CityBikes. No key required.

117 installs/wk local only
Adaga Network — Direct Booking Federation
by jeffreyturov-dev

Search and book every Adaga network hotel at once: live availability, exact prices, real booking.

3 tools answering
Scout
by dinewithscout

Find Resy restaurants and request reservations through Scout; the user approves every booking.

answering

Loyalist Reservations — questions

Answers built from our own checks of this server.

What can Loyalist Reservations do?
It exposes 5 tools, read directly from the server on our last check. Among them: book, find_venues, get_availability, get_reservation, join_waitlist. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Loyalist Reservations working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 416 ms. The bar chart above shows every period we have measured.
How do I connect Loyalist Reservations?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Loyalist Reservations need an API key?
No. Loyalist Reservations completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 5 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Loyalist Reservations?
It answers our handshake in 416 ms on average, which is faster than 31% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.