Remote MCP · Endpoint

Loyalist Reservations MCP server

No. Loyalist Reservations answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://agent.eatloyalist.com/mcp

The last check completed an MCP handshake.

Registry name
com.eatloyalist/restaurant-reservations
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
33 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Book tables at restaurants on the Loyalist network. No login; read availability, then book.
Listing
From the official MCP registry (active).
Recent checks of Loyalist Reservations
CheckedResultHandshake
1 hour agoHandshake completed33 ms
1 day agoHandshake completed31 ms
2 days agoHandshake completed25 ms
3 days agoHandshake completed24 ms
4 days agoHandshake completed30 ms
5 days agoHandshake completed59 ms
6 days agoHandshake completed30 ms
9 days agoHandshake completed25 ms
11 days agoHandshake completed34 ms
14 days agoHandshake completed349 ms
16 days agoHandshake completed50 ms
18 days agoHandshake completed28 ms
20 days agoHandshake completed26 ms
22 days agoHandshake completed49 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 14 responding of 14.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with Loyalist Reservations and makes no claim about it beyond what these checks measured.