Remote MCP · Endpoint

Whoppah MCP server

No. Whoppah answered an MCP handshake 52 minutes ago.

UpLast checked 52 minutes ago

Server URL

https://mcp.whoppah.com/mcp

The last check completed an MCP handshake.

Registry name
com.whoppah/commerce
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
525 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Search and shop curated second-hand design: furniture, lighting, art and designer bags.
Listing
From the official MCP registry (active).
Recent checks of Whoppah
CheckedResultHandshake
52 minutes agoHandshake completed525 ms
2 days agoHandshake completed211 ms
5 days agoHandshake completed513 ms
7 days agoHandshake completed230 ms
9 days agoHandshake completed345 ms
11 days agoHandshake completed218 ms
13 days agoHandshake completed379 ms
15 days agoHandshake completed436 ms
17 days agoHandshake completed208 ms
19 days agoHandshake completed172 ms
20 days agoHandshake completed205 ms
21 days agoHandshake completed481 ms
23 days agoHandshake completed688 ms
25 days agoHandshake completed225 ms

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

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