Remote MCP · Endpoint

Foodish MCP server

No. Foodish answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://gateway.pipeworx.io/foodish/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/foodish
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
98 ms
Tools exposed
46 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Foodish MCP.
Listing
From the official MCP registry (active).
Recent checks of Foodish
CheckedResultHandshake
2 hours agoHandshake completed98 ms
1 day agoHandshake completed173 ms
2 days agoHandshake completed103 ms
3 days agoHandshake completed59 ms
4 days agoHandshake completed98 ms
5 days agoHandshake completed62 ms
7 days agoHandshake completed206 ms
9 days agoHandshake completed194 ms
11 days agoHandshake completed86 ms
14 days agoHandshake completed67 ms
16 days agoHandshake completed58 ms
18 days agoHandshake completed66 ms
20 days agoHandshake completed81 ms
22 days agoHandshake completed71 ms
24 days agoHandshake completed54 ms
26 days agoHandshake completed50 ms
27 days agoHandshake completed64 ms
29 days agoHandshake completed71 ms

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

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