Remote MCP · Endpoint

PrepSheet MCP server

No. PrepSheet answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://getprepsheet.com/mcp

The last check completed an MCP handshake.

Registry name
com.getprepsheet/prepsheet
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
272 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Read-only kitchen costing, recipe scaling, UK GP, starter menus, and prep lists for chefs.
Listing
From the official MCP registry (deprecated).
Recent checks of PrepSheet
CheckedResultHandshake
1 hour agoHandshake completed272 ms
8 days agoHandshake completed272 ms
9 days agoHandshake completed259 ms
11 days agoHandshake completed276 ms
12 days agoHandshake completed315 ms
12 days agoHandshake completed281 ms
14 days agoHandshake completed277 ms
14 days agoHandshake completed273 ms
16 days agoHandshake completed265 ms
19 days agoHandshake completed268 ms
21 days agoHandshake completed264 ms
24 days agoHandshake completed263 ms
26 days agoHandshake completed269 ms
28 days agoHandshake completed260 ms

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

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