Skip to content

Loyalist Reservations

by eatloyalist.com · remote · no sign-in to list tools · v1.0.0 · published by com.eatloyalist

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

Changes · 2

5 tools: 2 change things and 3 only read.

Scanned Oct 21, 2026

1 check matched something in the tool definitions. No finding is not a safety guarantee. How the checks work.

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

Findings

Matches of fixed checks, with the text they matched.

1 info

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

5 tools

Changes things 2Claude Code: ask
  • bookBook a table.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Book a table
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • join_waitlistAsk to be told if a table opens at a time the guest actually wants.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Join the waitlist
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
Only reads 3Claude Code: allow
  • find_venuesRestaurants bookable through this network, and what each one's system supports.No findings

    Why it is in this group

    • The name "find_venues" says "find": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Find venues
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_availabilityBookable times at one venue, on one date, for one party size.No findings

    Why it is in this group

    • The name "get_availability" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Check availability
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_reservationRead one booking this credential made back from the venue.1 finding

    Why it is in this group

    • The name "get_reservation" says "get": a word for reading.

    Findings

    • Info

      The description mentions "credential".

      Matched text

      description: "Read one booking this credential made back from the venue. Use..."

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Look up a reservation
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__restaurant-reservations__find_venues",
      "mcp__restaurant-reservations__get_availability",
      "mcp__restaurant-reservations__get_reservation"
    ],
    "ask": [
      "mcp__restaurant-reservations__book",
      "mcp__restaurant-reservations__join_waitlist"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as restaurant-reservations. Review it before you use it.