Loyalist Reservations MCP server
com.eatloyalist/restaurant-reservationseatloyalist.comstreamable-httpv1.0.0Scanned
Book tables at restaurants on the Loyalist network. No login; read availability, then book.
5 tools: 2 change things and 3 only read.
- Reads private data · 1
- Reads text others write · 2
- Can send data out · 2
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
2 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Loyalist Reservations MCP server can do
The Loyalist Reservations MCP server is published by eatloyalist.com, a domain the MCP Registry verified. It has 5 tools. It can create or change data (2 tools: book and join_waitlist), but cannot delete data. 3 tools only read.
1 tool reads private data (get_reservation); 2 tools bring in text other people can write (book and join_waitlist); 2 tools can send data out of your system (book and join_waitlist). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.
The fixed checks matched 1 finding (credentials-mention). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 13, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
5 tools
Changes things 2Claude Code: ask
bookBook a table.Reads text others writeCan send data outNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe input takes a destination (input.phone): what the tool writes goes there.
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.Reads text others writeCan send data outNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe input takes a destination (input.phone): what the tool writes goes there.
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 3Show 3 read-only tools
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.Reads private data1 finding
Why it is in this group
- The name "get_reservation" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "read" and "credential": it reads secrets.
Findings
- Info
The description mentions "credential".
What this check looks forMatched text
description: "Read one booking this credential made back from the venue. Use..."
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.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
4 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 private-data tool breaks every one.
- Reads private data1
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write2
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out2
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
{
"permissions": {
"deny": [
"mcp__restaurant-reservations__get_reservation"
]
}
}Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:37 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 2
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://agent.eatloyalist.com/.well-known/oauth-protected-resource/mcp
- Authorization servers
- https://agent.eatloyalist.com
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- no
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://agent.eatloyalist.com/mcp: tools/list returned 5 tools to an anonymous client, including book (write), join_waitlist (write)
Findings
Matches of fixed checks, with the text they matched.
- Infoget_reservation
The description mentions "credential".
What this check looks forMatched text
description: "Read one booking this credential made back from the venue. Use..."
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
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/mcpclaude mcp add --transport http restaurant-reservations https://agent.eatloyalist.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .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. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as restaurant-reservations. Review it before you use it.
Capability tags behind 3 rules
- mcp__restaurant-reservations__book untrusted-input, outbound
- mcp__restaurant-reservations__get_reservation private-data
- mcp__restaurant-reservations__join_waitlist untrusted-input, outbound
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.eatloyalist/restaurant-reservations/verify?hash=d06ae3def1e60fbfc8c67f15ff40fc9ddba50a9d0b03e7d4bbad864f834c5646" | jq -e '.changed == false'Pinned hash d06ae3def1e6, from Nov 13, 2026, 02:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.eatloyalist/restaurant-reservations/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.eatloyalist/restaurant-reservations)Source: MCP Registry. Synced Oct 21, 2026, 17:54 UTC.
Loyalist Reservations MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Loyalist Reservations MCP server safe?
- No scan can promise that. What its definitions show: 5 tools, 2 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Loyalist Reservations MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Loyalist Reservations MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Loyalist Reservations MCP server have?
- 5 tools: 2 write, 3 read. book, join_waitlist, find_venues, get_availability and get_reservation.
Does the Loyalist Reservations MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Loyalist Reservations MCP server send data to outside services?
- 2 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): book and join_waitlist.
Has the Loyalist Reservations MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 13, 2026.