Remote MCP · Endpoint

io.github.Anon2052/price-tracker-mcp MCP server

No. io.github.Anon2052/price-tracker-mcp answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://price-tracker-mcp.onrender.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.Anon2052/price-tracker-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
136 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Price-check product pages and build affiliate tracking links.
Listing
From the official MCP registry (active).
Recent checks of io.github.Anon2052/price-tracker-mcp
CheckedResultHandshake
1 hour agoHandshake completed136 ms
8 days agoHandshake completed316 ms
9 days agoHandshake completed135 ms
11 days agoHandshake completed288 ms
12 days agoHandshake completed169 ms
12 days agoHandshake completed516 ms
14 days agoHandshake completed163 ms
14 days agoHandshake completed177 ms
16 days agoHandshake completed326 ms
19 days agoHandshake completed259 ms
21 days agoHandshake completed268 ms
24 days agoHandshake completed281 ms
26 days agoHandshake completed144 ms
28 days agoHandshake completed267 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 io.github.Anon2052/price-tracker-mcp and makes no claim about it beyond what these checks measured.