# Loyalist Reservations (remote · agent.eatloyalist.com) Book tables at restaurants on the Loyalist network. No login; read availability, then book. - Trust score: 78/100 (medium) - Change this week: +3 - Registry status: active - Liveness: live - Owner verified: no - Last scored: 2026-11-05 ## Components - remote · `agent.eatloyalist.com`: 78/100 (this document), [markdown](https://verifymcp.io/servers/com-eatloyalist-restaurant-reservations/agent.md), [page](https://verifymcp.io/servers/com-eatloyalist-restaurant-reservations/agent) ## Channel facts - Endpoint: `https://agent.eatloyalist.com/mcp` - Transports: `streamable-http` - Auth: `none` - Version: `1.0.0` ## Trust breakdown How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog) Scored 2026-11-05. - **Endpoint Security**: 80/100 - The endpoint's TLS certificate is valid, in date, and uses a strong key. - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. - HTTPS is enforced; there's no plaintext access path. - The HSTS (Strict-Transport-Security) header is present. - DNSSEC check failed: this domain isn't protected by DNSSEC. - **Transport & Reachability**: 100/100 - Verified streamable-http transport via a live MCP handshake. - **Schema Quality & AI Usability**: 57/100 - AI-judged instruction clarity (good). - Context-footprint check failed: tool/resource definitions use about 1757 tokens (~351/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. - Usage-examples check failed: none of the tools include examples. - **Stability & Change Management**: 73/100 - Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses. - **Tool Coverage**: 67/100 - 100% of tools have a non-trivial description (not blank, and not just the tool's name). - 0% of tool parameters carry a description. - **Tool Safety**: 100/100 - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured. - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation. - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it. - **Capabilities**: 100/100 - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28. ## Install ### How do I install the Loyalist Reservations MCP server? Loyalist Reservations is a hosted endpoint at https://agent.eatloyalist.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation. ### Claude ```bash claude mcp add --transport http com-eatloyalist-restaurant-reservations 'https://agent.eatloyalist.com/mcp' ``` ### Cursor ```json { "mcpServers": { "com-eatloyalist-restaurant-reservations": { "url": "https://agent.eatloyalist.com/mcp" } } } ``` ### VS Code ```json { "servers": { "com-eatloyalist-restaurant-reservations": { "type": "http", "url": "https://agent.eatloyalist.com/mcp" } } } ``` ### Codex ```toml [mcp_servers.com-eatloyalist-restaurant-reservations] url = "https://agent.eatloyalist.com/mcp" ``` ### opencode ```json { "$schema": "https://opencode.ai/config.json", "mcp": { "com-eatloyalist-restaurant-reservations": { "type": "remote", "url": "https://agent.eatloyalist.com/mcp", "enabled": true } } } ``` ### OpenClaw ```bash openclaw mcp add com-eatloyalist-restaurant-reservations --url 'https://agent.eatloyalist.com/mcp' --transport streamable-http ``` ### Hermes ```yaml mcp_servers: com-eatloyalist-restaurant-reservations: url: "https://agent.eatloyalist.com/mcp" ``` ### Netclaw ```json { "McpServers": { "com-eatloyalist-restaurant-reservations": { "Transport": "http", "Url": "https://agent.eatloyalist.com/mcp" } } } ``` ### Vellum ```bash assistant mcp add com-eatloyalist-restaurant-reservations -t streamable-http -u 'https://agent.eatloyalist.com/mcp' ``` ### Other ```json { "mcpServers": { "com-eatloyalist-restaurant-reservations": { "type": "http", "url": "https://agent.eatloyalist.com/mcp" } } } ``` The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs. ## Changelog Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims. ### 2026-11-05 (score 78, +1) No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-11-03 (score 77, +1) No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-10-31 (score 76, +1) No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-10-29 (score 75, +1) - [functional] Server version: 1.28.1 → 1.30.0 ### 2026-10-27 (score 74, +1) No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-10-25 (score 73, +1) No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-10-23 (score 72, +1) No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-10-21 (score 71, +1) - [security] The server rewrote its instructions, which are the text every model session reads - [security] The server changed its declared name: loyalist-reservations → orion-reservations - [security] Tool “find_venues” rewrote its description, which is the text the model reads ## MCP tools (5) ### `find_venues` (~172 tokens) 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. Input parameters: - `signup_form_id` - `venue_id` ### `get_availability` (~155 tokens) 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. Input parameters: - `date` (string, required) - `party_size` (integer, required) - `venue_id` (string, required) ### `book` (~345 tokens) 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. Input parameters: - `email` (string, required) - `first_name` (string, required) - `last_name` (string, required) - `note` - `phone` - `slot_id` (string, required) - `source` ### `get_reservation` (~78 tokens) 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. Input parameters: - `reservation_id` (string, required) ### `join_waitlist` (~476 tokens) 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. Input parameters: - `date` (string, required) - `email` (string, required) - `first_name` (string, required) - `last_name` (string, required) - `notes` - `party_size` (integer, required) - `phone` - `time_range` (string, required) - `venue_id` (string, required) ## Diagnostics Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-eatloyalist-restaurant-reservations/agent#diagnostics ## Score history - 2026-11-05: 78 - 2026-11-04: 77 - 2026-11-03: 77 - 2026-11-02: 76 - 2026-11-01: 76 - 2026-10-31: 76 - 2026-10-30: 75 - 2026-10-29: 75 - 2026-10-28: 74 - 2026-10-27: 74 - 2026-10-26: 73 - 2026-10-25: 73 - 2026-10-24: 72 - 2026-10-23: 72 - 2026-10-22: 71 - 2026-10-21: 71 - 2026-10-20: 70 - 2026-10-19: 70 - 2026-10-18: 69 - 2026-10-17: 69 - 2026-10-16: 69 - 2026-10-15: 68 - 2026-10-14: 68 ## Common questions ### What is the Loyalist Reservations MCP server? Loyalist Reservations is an MCP server listed in the public MCP registry as com.eatloyalist/restaurant-reservations. Book tables at restaurants on the Loyalist network. No login; read availability, then book. This page covers its hosted endpoint (https://agent.eatloyalist.com/mcp). ### Is the Loyalist Reservations MCP server safe to use? Loyalist Reservations scores 78 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm. ### What tools does the Loyalist Reservations MCP server expose? Loyalist Reservations exposes 5 tools: find_venues, get_availability, book, get_reservation, join_waitlist. Their descriptions and schemas cost roughly 1,226 tokens of context every time the server is loaded. ### Does the Loyalist Reservations MCP server require authentication? No. We connected to Loyalist Reservations without credentials and it answered, so anything it exposes is reachable by anyone who knows the address. ### Is the Loyalist Reservations MCP server still maintained? Loyalist Reservations is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced. ### What did VerifyMCP test on the Loyalist Reservations MCP server? VerifyMCP ran 13 checks on Loyalist Reservations, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out. ## Links - Remote endpoint: https://agent.eatloyalist.com/mcp - Changelog RSS feed: https://verifymcp.io/servers/com-eatloyalist-restaurant-reservations/agent.xml - Changelog JSON feed: https://verifymcp.io/servers/com-eatloyalist-restaurant-reservations/agent/changelog.json - Trust report (JSON): https://verifymcp.io/servers/com-eatloyalist-restaurant-reservations/agent.json - HTML version of this page: https://verifymcp.io/servers/com-eatloyalist-restaurant-reservations/agent