Remote MCP · Endpoint

Dish Directory MCP server

No. Dish Directory answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://dishdirectory.com/mcp

The last check completed an MCP handshake.

Registry name
com.dishdirectory/dishdirectory
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
148 ms
Tools exposed
11 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Restaurants and their signature dishes across the US and Canada.
Listing
From the official MCP registry (active).
Recent checks of Dish Directory
CheckedResultHandshake
2 hours agoHandshake completed148 ms
1 day agoHandshake completed79 ms
3 days agoHandshake completed74 ms
3 days agoHandshake completed105 ms
4 days agoHandshake completed392 ms
5 days agoHandshake completed250 ms
7 days agoHandshake completed128 ms
10 days agoHandshake completed143 ms
12 days agoHandshake completed272 ms
15 days agoHandshake completed144 ms
17 days agoHandshake completed131 ms
19 days agoHandshake completed184 ms
21 days agoHandshake completed1.79 s
23 days agoHandshake completed1.68 s
25 days agoHandshake completed124 ms

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

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 Dish Directory and makes no claim about it beyond what these checks measured.