Remote MCP · Endpoint

Pinflower — flowers in Prague MCP server

No. Pinflower — flowers in Prague answered an MCP handshake 35 minutes ago.

UpLast checked 35 minutes ago

Server URL

https://pinflower.cz/api/mcp

The last check completed an MCP handshake.

Registry name
cz.pinflower/flowers
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
1.30 s
Tools exposed
9 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Order bouquets from independent Prague florists: live prices, delivery times, pay on pinflower.cz.
Listing
From the official MCP registry (active).
Recent checks of Pinflower — flowers in Prague
CheckedResultHandshake
35 minutes agoHandshake completed1.30 s
9 days agoHandshake completed1.03 s
10 days agoHandshake completed768 ms
11 days agoHandshake completed883 ms
12 days agoHandshake completed877 ms
14 days agoHandshake completed1.06 s
14 days agoHandshake completed410 ms
15 days agoHandshake completed1.20 s
17 days agoHandshake completed1.02 s
19 days agoHandshake completed1.34 s
21 days agoHandshake completed1.12 s
24 days agoHandshake completed1.37 s
26 days agoHandshake completed968 ms
28 days agoHandshake completed1.02 s

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

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 Pinflower — flowers in Prague and makes no claim about it beyond what these checks measured.