Remote MCP · Endpoint

PetalPal Plant Care MCP server

No. PetalPal Plant Care answered an MCP handshake 9 hours ago.

UpLast checked 9 hours ago

Server URL

https://petalpal.top/api/mcp/

The last check completed an MCP handshake.

Registry name
top.petalpal/plant-care
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
100 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 11 checks
Described by its publisher as
Plant and flower care for 202 species in ten languages, with source links and editorial status.
Listing
From the official MCP registry (active).
Recent checks of PetalPal Plant Care
CheckedResultHandshake
9 hours agoHandshake completed100 ms
4 days agoHandshake completed931 ms
14 days agoHandshake completed108 ms
15 days agoHandshake completed1.00 s
15 days agoHandshake completed969 ms
17 days agoHandshake completed1.05 s
18 days agoHandshake completed82 ms
19 days agoHandshake completed916 ms
20 days agoHandshake completed173 ms
21 days agoHandshake completed95 ms
23 days agoHandshake completed99 ms

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

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