Remote MCP · Endpoint

Blumee — flower delivery comparison (Germany) MCP server

No. Blumee — flower delivery comparison (Germany) answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://api.blumee.app/mcp

The last check completed an MCP handshake.

Registry name
app.blumee/flowers
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
472 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Compare flower delivery in Germany: find bouquets by text or photo, order at partner florists.
Listing
From the official MCP registry (active).
Recent checks of Blumee — flower delivery comparison (Germany)
CheckedResultHandshake
1 hour agoHandshake completed472 ms
1 day agoHandshake completed179 ms
3 days agoHandshake completed484 ms
5 days agoHandshake completed482 ms
8 days agoHandshake completed474 ms
10 days agoHandshake completed540 ms
12 days agoHandshake completed488 ms
14 days agoHandshake completed523 ms
16 days agoHandshake completed531 ms
18 days agoHandshake completed782 ms
20 days agoHandshake completed470 ms
22 days agoHandshake completed462 ms
23 days agoHandshake completed575 ms

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

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 Blumee — flower delivery comparison (Germany) and makes no claim about it beyond what these checks measured.