Remote MCP · Endpoint

Loafy: Sourdough Bread Baking MCP server

No. Loafy: Sourdough Bread Baking answered an MCP handshake 13 minutes ago.

UpLast checked 13 minutes ago

Server URL

https://loafy.ai/mcp

The last check completed an MCP handshake.

Registry name
ai.loafy/loafy
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
474 ms
Tools exposed
21 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Sourdough and pizza: dough calculators, the Bake Planner, The Sourdough Framework, your bake journal
Listing
From the official MCP registry (active).
Recent checks of Loafy: Sourdough Bread Baking
CheckedResultHandshake
13 minutes agoHandshake completed474 ms
9 days agoHandshake completed171 ms
9 days agoHandshake completed524 ms
11 days agoHandshake completed561 ms
12 days agoHandshake completed541 ms
13 days agoHandshake completed585 ms
14 days agoHandshake completed525 ms
15 days agoHandshake completed660 ms
16 days agoHandshake completed724 ms
19 days agoHandshake completed504 ms
21 days agoHandshake completed488 ms
24 days agoHandshake completed555 ms
26 days agoHandshake completed549 ms
28 days agoHandshake completed643 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 Loafy: Sourdough Bread Baking and makes no claim about it beyond what these checks measured.