Remote MCP · Endpoint

Pandough MCP server

No. Pandough answered an MCP handshake 9 hours ago.

UpLast checked 9 hours ago

Server URL

https://pandough.app/api/mcp

The last check completed an MCP handshake.

Registry name
app.pandough/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
100 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Flour-first dough plans: yeast, hydration, schedule from flour you own. No API key for plan tools.
Listing
From the official MCP registry (active).
Recent checks of Pandough
CheckedResultHandshake
9 hours agoHandshake completed100 ms
2 days agoHandshake completed207 ms
4 days agoHandshake completed174 ms
5 days agoHandshake completed151 ms
7 days agoHandshake completed346 ms
8 days agoHandshake completed109 ms
9 days agoHandshake completed656 ms
12 days agoHandshake completed631 ms
13 days agoHandshake completed606 ms
15 days agoHandshake completed504 ms
16 days agoHandshake completed101 ms
18 days agoHandshake completed68 ms
19 days agoHandshake completed149 ms
19 days agoHandshake completed423 ms
20 days agoHandshake completed104 ms
21 days agoHandshake completed610 ms
23 days agoHandshake completed608 ms

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

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