Remote MCP · Endpoint

Panda Greetings MCP server

No. Panda Greetings answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://www.pandagreetings.com/mcp/designs

The last check completed an MCP handshake.

Registry name
com.pandagreetings/cards
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
259 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Printed greeting cards: find designs with your message inside, then order on our site.
Listing
From the official MCP registry (active).
Recent checks of Panda Greetings
CheckedResultHandshake
1 hour agoHandshake completed259 ms
2 days agoHandshake completed330 ms
5 days agoHandshake completed301 ms
7 days agoHandshake completed300 ms
9 days agoHandshake completed190 ms
11 days agoHandshake completed204 ms
13 days agoHandshake completed360 ms
15 days agoHandshake completed192 ms
17 days agoHandshake completed178 ms
19 days agoHandshake completed407 ms
20 days agoHandshake completed303 ms
21 days agoHandshake completed378 ms
23 days agoHandshake completed393 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 Panda Greetings and makes no claim about it beyond what these checks measured.