Loyalist Reservations

com.eatloyalist/restaurant-reservationsVersion 1.0.0

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

Status

Responds343 msNov 14, 2026, 13:54 UTCAnswered our handshake without sign-in.

Registry data may be out of date

We could not refresh it, so this page shows the last copy.

Last checked: Nov 14, 2026, 13:54 UTC
Latency: 343 ms
Remotes responding: 1 of 1
Sign-in: No sign-in
Hosting: Hosted outside the EU (detected)
Registry data as of: Nov 14, 2026, 22:14 UTC

Data from the official MCP Registry, checked by run.zero. How we check

Connect

Streamable HTTP

https://agent.eatloyalist.com/mcpResponds343 msNov 14, 2026, 13:54 UTC

No sign-in

Claude Code

claude mcp add --transport http restaurant-reservations https://agent.eatloyalist.com/mcp

Claude Desktop and claude.ai

1
2
3

Settings > Connectors > Add custom connector
Name: restaurant-reservations
Remote MCP server URL: https://agent.eatloyalist.com/mcp

Cursor

{
  "mcpServers": {
    "restaurant-reservations": {
      "url": "https://agent.eatloyalist.com/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"restaurant-reservations","type":"http","url":"https://agent.eatloyalist.com/mcp"}'

Built your own server? run.zero hosts MCP servers on European infrastructure.

Host your own MCP server on run.zero

Tools

5 tools

Tools of Loyalist Reservations
	Description		Read-only	Idempotent	Open world
`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.	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.	No	No	No	Yes
`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.	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.	No	Yes	Yes	No
`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.	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.	No	Yes	Yes	No
`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.	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.	No	Yes	Yes	No
`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.	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.	No	No	No	Yes

Details

Registry status: Active
Published: Oct 14, 2026
Updated: Oct 14, 2026
Website: Not given
Repository: Not given
Categories: Uncategorized
GDPR: Not declared

Are you the operator? Claim this listing