Remote MCP · Endpoint

WaitApp MCP server

No. WaitApp answered an MCP handshake 34 minutes ago.

UpLast checked 34 minutes ago

Server URL

https://waitapp.online/api/mcp/

The last check completed an MCP handshake.

Registry name
online.waitapp/waitapp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
667 ms
Tools exposed
33 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Find venues, book tables, rooms and services, buy event tickets and order food delivery.
Listing
From the official MCP registry (active).
Recent checks of WaitApp
CheckedResultHandshake
34 minutes agoHandshake completed667 ms
9 days agoHandshake completed406 ms
10 days agoHandshake completed492 ms
11 days agoHandshake completed425 ms
12 days agoHandshake completed617 ms
14 days agoHandshake completed287 ms
14 days agoHandshake completed700 ms
15 days agoHandshake completed291 ms
17 days agoHandshake completed452 ms
19 days agoHandshake completed583 ms
21 days agoHandshake completed536 ms
24 days agoHandshake completed396 ms
26 days agoHandshake completed673 ms
28 days agoHandshake completed180 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 WaitApp and makes no claim about it beyond what these checks measured.