Loyalist MCP server

• Registry namecom.eatloyalist/restaurant-reservationsverified in the MCP registry

The registry name sits under eatloyalist.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-20
• Tools5
• Server calls itselfloyalist-reservations
• Server version1.28.1
• Protocol version2025-06-18

On 2026-10-20 the server answered initialize and tools/list without a sign-in. First answer in 294 ms.

• Whether its tools do the product's job has not been judged yet.
• Checked on 2 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP scoreafter a weeka score needs 7 daily checks: 2 so far
• Answeredmeasuring2 of the 7 daily checks it takes to print a share
• Median first answer232 ms
• Space in an agent's context≈ 1,727 tokensthe definitions of all its tools (5), which an agent carries on every turn
• Tool definitionsB · 83 of 100
• Typed results0 of 5 toolsdeclared outputSchema: results come typed, read once

• Parameters without a description: in 5 of 5

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (30%), doing the product's job (25%), definitions (20%), context (10%) and use (15%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• 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…

• 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…

• 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…

• 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…

• 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…