Remote MCP · Endpoint

io.github.DataLeadsPRO/amazon-product-data MCP server

No. io.github.DataLeadsPRO/amazon-product-data answered an MCP handshake 3 hours ago.

UpLast checked 3 hours ago

Server URL

https://data.dataleads.pro/mcp/amazon-product-data

The last check completed an MCP handshake.

Registry name
io.github.DataLeadsPRO/amazon-product-data
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
333 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Amazon search and product extraction: titles, prices, ASINs, and listings as clean JSON.
Listing
From the official MCP registry (active).
Recent checks of io.github.DataLeadsPRO/amazon-product-data
CheckedResultHandshake
3 hours agoHandshake completed333 ms
2 days agoHandshake completed455 ms
4 days agoHandshake completed354 ms
5 days agoHandshake completed277 ms
7 days agoHandshake completed298 ms
8 days agoHandshake completed284 ms
9 days agoHandshake completed339 ms
12 days agoHandshake completed495 ms
13 days agoHandshake completed303 ms
15 days agoHandshake completed313 ms
16 days agoHandshake completed278 ms
17 days agoHandshake completed279 ms
18 days agoHandshake completed294 ms
19 days agoHandshake completed552 ms
20 days agoHandshake completed421 ms
21 days agoHandshake completed459 ms
22 days agoHandshake completed474 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/amazon-product-data and makes no claim about it beyond what these checks measured.