Remote MCP · Endpoint

io.github.DataLeadsPRO/website-change-monitor MCP server

No. io.github.DataLeadsPRO/website-change-monitor answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://data.dataleads.pro/mcp/website-change-monitor

The last check completed an MCP handshake.

Registry name
io.github.DataLeadsPRO/website-change-monitor
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
98 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Track page and price changes over time: diffs, history, and alerts through simple tracking
Listing
From the official MCP registry (active).
Recent checks of io.github.DataLeadsPRO/website-change-monitor
CheckedResultHandshake
2 hours agoHandshake completed98 ms
2 days agoHandshake completed100 ms
4 days agoHandshake completed128 ms
5 days agoHandshake completed98 ms
7 days agoHandshake completed101 ms
8 days agoHandshake completed109 ms
9 days agoHandshake completed104 ms
12 days agoHandshake completed98 ms
14 days agoHandshake completed100 ms
15 days agoHandshake completed105 ms
17 days agoHandshake completed98 ms
18 days agoHandshake completed118 ms
19 days agoHandshake completed106 ms
20 days agoHandshake completed133 ms
20 days agoHandshake completed117 ms
21 days agoHandshake completed457 ms
23 days agoHandshake completed647 ms

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

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.DataLeadsPRO/website-change-monitor and makes no claim about it beyond what these checks measured.