Remote MCP · Endpoint

McpStamp Price Tracker MCP server

No. McpStamp Price Tracker answered an MCP handshake 20 minutes ago.

UpLast checked 20 minutes ago

Server URL

https://mcp.zovo.one/mcp/price-tracker

The last check completed an MCP handshake.

Registry name
io.github.theluckystrike/price-tracker-drop-alert-watch
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
1.07 s
Tools exposed
10 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Read a shop page's current price, watch items with a target price and see each item's history.
Listing
From the official MCP registry (active).
Recent checks of McpStamp Price Tracker
CheckedResultHandshake
20 minutes agoHandshake completed1.07 s
9 days agoHandshake completed58 ms
9 days agoHandshake completed97 ms
11 days agoHandshake completed42 ms
12 days agoHandshake completed87 ms
13 days agoHandshake completed74 ms
14 days agoHandshake completed63 ms
15 days agoHandshake completed98 ms
16 days agoHandshake completed186 ms
19 days agoHandshake completed28 ms
22 days agoHandshake completed55 ms
24 days agoHandshake completed40 ms
26 days agoHandshake completed40 ms
28 days agoHandshake completed151 ms

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

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