Remote MCP · Endpoint

Safe Bite MCP server

No. Safe Bite answered an MCP handshake 52 minutes ago.

UpLast checked 52 minutes ago

Server URL

https://www.safebiter.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.AndrewVG23/safe-bite
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
129 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Restaurant inspections for Chicago, NYC, Minneapolis, Milwaukee, Austin, and Denver.
Listing
From the official MCP registry (active).
Recent checks of Safe Bite
CheckedResultHandshake
52 minutes agoHandshake completed129 ms
3 days agoHandshake completed52 ms
12 days agoHandshake completed93 ms
13 days agoHandshake completed116 ms
14 days agoHandshake completed2.31 s
15 days agoHandshake completed64 ms
17 days agoHandshake completed4.60 s
18 days agoHandshake completed75 ms
18 days agoHandshake completed4.01 s
20 days agoHandshake completed90 ms
22 days agoHandshake completed99 ms
25 days agoHandshake completed4.47 s
27 days agoHandshake completed78 ms
29 days agoHandshake completed116 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 Safe Bite and makes no claim about it beyond what these checks measured.