Remote MCP · Endpoint

KaleMap dietary menu finder MCP server

No. KaleMap dietary menu finder answered an MCP handshake 17 hours ago.

UpLast checked 17 hours ago

Server URL

https://kalemap.com/mcp

The last check completed an MCP handshake.

Registry name
com.kalemap/menu
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
344 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 12 checks
Described by its publisher as
Find restaurants and sourced dietary dish evidence. Free discovery; metered menus need an API key.
Listing
From the official MCP registry (active).
Recent checks of KaleMap dietary menu finder
CheckedResultHandshake
17 hours agoHandshake completed344 ms
11 days agoHandshake completed313 ms
12 days agoHandshake completed392 ms
12 days agoHandshake completed545 ms
14 days agoHandshake completed587 ms
15 days agoHandshake completed283 ms
16 days agoHandshake completed53 ms
17 days agoHandshake completed61 ms
18 days agoHandshake completed525 ms
20 days agoHandshake completed383 ms
22 days agoHandshake completed183 ms
25 days agoHandshake completed152 ms

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

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 KaleMap dietary menu finder and makes no claim about it beyond what these checks measured.