Remote MCP · Endpoint

EveryHourDeal Shopping MCP server

No. EveryHourDeal Shopping answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://everyhourdeal-checkout.cybermax-tools.workers.dev/mcp

The last check completed an MCP handshake.

Registry name
com.everyhourdeal/shopping
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
144 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Search, compare and get deals on 1,800 US-warehouse home, patio, gym and pet products.
Listing
From the official MCP registry (active).
Recent checks of EveryHourDeal Shopping
CheckedResultHandshake
2 hours agoHandshake completed144 ms
2 days agoHandshake completed81 ms
4 days agoHandshake completed171 ms
6 days agoHandshake completed98 ms
9 days agoHandshake completed86 ms
11 days agoHandshake completed74 ms
13 days agoHandshake completed155 ms
14 days agoHandshake completed85 ms
16 days agoHandshake completed81 ms
17 days agoHandshake completed182 ms
18 days agoHandshake completed343 ms
21 days agoHandshake completed64 ms
22 days agoHandshake completed94 ms
24 days agoHandshake completed106 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 EveryHourDeal Shopping and makes no claim about it beyond what these checks measured.