Remote MCP · Endpoint

RestaurantDoctorAI MCP server

No. RestaurantDoctorAI answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://restaurantdoctorai.com/api/mcp

The last check completed an MCP handshake.

Registry name
com.restaurantdoctorai/profit-check
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
124 ms
Tools exposed
22 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Free restaurant profit check, recipe costing, calculators, website check, deadlines, guides, blog.
Listing
From the official MCP registry (active).
Recent checks of RestaurantDoctorAI
CheckedResultHandshake
2 hours agoHandshake completed124 ms
10 days agoHandshake completed153 ms
11 days agoHandshake completed304 ms
11 days agoHandshake completed115 ms
13 days agoHandshake completed122 ms
14 days agoHandshake completed126 ms
15 days agoHandshake completed153 ms
16 days agoHandshake completed245 ms
17 days agoHandshake completed105 ms
19 days agoHandshake completed192 ms
22 days agoHandshake completed530 ms
24 days agoHandshake completed100 ms
26 days agoHandshake completed105 ms
29 days agoHandshake completed188 ms

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

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