Remote MCP · Endpoint

Thmenu MCP server

No. Thmenu answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.thmenu.com/

The last check completed an MCP handshake.

Registry name
com.thmenu/thmenu
Transport
Streamable HTTP
Protocol negotiated
2025-03-26
Handshake latency
126 ms
Tools exposed
27 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Restaurant menus, carts, reservations and owner drafts for AI agents (Thmenu MCP).
Website
https://thmenu.com/
Listing
From the official MCP registry (active).
Recent checks of Thmenu
CheckedResultHandshake
1 hour agoHandshake completed126 ms
2 days agoHandshake completed305 ms
4 days agoHandshake completed141 ms
7 days agoHandshake completed157 ms
9 days agoHandshake completed90 ms
11 days agoHandshake completed35 ms
13 days agoHandshake completed123 ms
15 days agoHandshake completed68 ms
16 days agoHandshake completed62 ms
18 days agoHandshake completed82 ms
19 days agoHandshake completed270 ms
20 days agoHandshake completed102 ms
23 days agoHandshake completed80 ms
24 days agoHandshake completed124 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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

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