Loyalist Reservations

com.eatloyalist由 eatloyalist.com 发布官方发布者v1.0.0更新于 Oct 27, 2026

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

已验证Streamable HTTP可网页运行位置与生活效率与工作流

概览

AI 生成的概览

让助手在 Loyalist 网络的餐厅中查找可订餐厅、查询空位、预订餐位、查看预订状态并加入候补名单。

可以做什么
  • 查找可预订的餐厅,可按报名表单或其他条件缩小范围
  • 按日期和人数查询某家餐厅的可订时段,返回时段 ID 和餐厅当地时间
  • 使用空位结果中的时段 ID 预订餐位
  • 读取同一凭据所做的预订,确认是否成功
  • 为客人想要的时间申请加入候补名单,但不占用餐位
适用场景
适合让助手在 Loyalist 网络上查询餐厅空位并完成订位,或在心仪时段有空位时得到通知。适用于餐厅、日期、时间和人数都已确认的对话式用餐安排。
运行要求
远程 MCP 端点 agent.eatloyalist.com,使用 streamable HTTP;未声明登录、软件包、环境变量或请求头。查询空位需要餐厅当地日期和用餐人数。
安装前请注意
预订会占用真实餐厅的真实餐位,且没有取消工具,误订需由客人通过餐厅撤销;调用前应先与本人确认餐厅、日期、时间和人数,切勿试探性预订。pending 状态表示尚未回复,并非失败。候补申请不是预订,也不会保留餐位。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Loyalist Reservations,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Web executable,通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体,或 SourceWeft 对话中。智能体会读取该服务器的安装指南,先向你展示发布者、端点和登录方式,经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/com.eatloyalist%2Frestaurant-reservations/install.md,并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前,先告诉我它的发布者、端点和登录方式,等我确认。不要把 API 密钥写进命令或我会提交的文件;问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。

{
  "mcpServers": {
    "loyalist-reservations": {
      "type": "http",
      "url": "https://agent.eatloyalist.com/mcp"
    }
  }
}

工具

5

find_venues

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.

输入参数venue_idsignup_form_id

get_availability

Check 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.

输入参数date必填venue_id必填party_size必填

book

Book a table

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.

输入参数noteemail必填phonesourceslot_id必填last_name必填first_name必填

get_reservation

Look up a 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.

输入参数reservation_id必填

join_waitlist

Join the 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.

输入参数date必填email必填notesphonevenue_id必填last_name必填first_name必填party_size必填time_range必填

版本历史

1
  1. v1.0.0最新Oct 14, 2026

评分

已满足适用检查项的 83%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分
  • 已声明认证方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 图标10 分
  • 文档15 分

    请声明包含 README 的 GitHub 仓库,或在 OAuth 受保护资源元数据中提供 resource_documentation。

  • 许可证不适用

    托管服务按其提供方的条款使用,因此这里不要求许可证。此检查项不计入百分比。