Remote MCP · Endpoint

Pinoyshki Bakery MCP server

No. Pinoyshki Bakery answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://bot.pinoyshki.com/mcp

The last check completed an MCP handshake.

Registry name
com.pinoyshki/bakery
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
211 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 16 checks
Described by its publisher as
Browse Pinoyshki Bakery's menu, check an order against its rules, and get the checkout link.
Listing
From the official MCP registry (active).
Recent checks of Pinoyshki Bakery
CheckedResultHandshake
1 hour agoHandshake completed211 ms
2 days agoHandshake completed201 ms
4 days agoHandshake completed230 ms
6 days agoHandshake completed197 ms
7 days agoHandshake completed213 ms
9 days agoHandshake completed217 ms
10 days agoHandshake completed211 ms
11 days agoHandshake completed199 ms
14 days agoHandshake completed201 ms
15 days agoHandshake completed199 ms
17 days agoHandshake completed206 ms
18 days agoHandshake completed203 ms
19 days agoHandshake completed201 ms
21 days agoHandshake completed201 ms
22 days agoHandshake completed207 ms
22 days agoHandshake completed202 ms

The last 16 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 Pinoyshki Bakery and makes no claim about it beyond what these checks measured.