io.github.DataLeadsPRO/amazon-product-data is an MCP server published by io.github.DataLeadsPRO, hosted at data.dataleads.pro. When last checked on 2026-11-21 it was working: it answers and lists its tools. It declares 2 tools, including amazon_search, amazon_product.
Amazon search and product extraction: titles, prices, ASINs, and listings as clean JSON.
75 connections through 5 shared values. Tap any node.
Inferred from the host name and headers: what a server runs on, not who runs it.
V1 Amazon Search
| Parameter | Type | Description |
|---|---|---|
| query | string | |
| country | string | |
| language | string | |
| maxTimeout | integer |
{
"name": "amazon_search",
"description": "V1 Amazon Search",
"inputSchema": {
"type": "object",
"title": "amazon_searchArguments",
"properties": {
"query": {
"type": "string",
"title": "Query",
"default": null
},
"country": {
"type": "string",
"title": "Country",
"default": null
},
"language": {
"type": "string",
"title": "Language",
"default": null
},
"maxTimeout": {
"type": "integer",
"title": "Maxtimeout",
"default": null
}
}
}
}None yet. Changes appear after a server's second daily check.
Squares are this server's values; dots are other servers sharing them. A shared address or publisher is a lead, not proof of a common operator.
V1 Amazon Product
| Parameter | Type | Description |
|---|---|---|
| url | string | |
| maxTimeout | integer |
{
"name": "amazon_product",
"description": "V1 Amazon Product",
"inputSchema": {
"type": "object",
"title": "amazon_productArguments",
"properties": {
"url": {
"type": "string",
"title": "Url",
"default": null
},
"maxTimeout": {
"type": "integer",
"title": "Maxtimeout",
"default": null
}
}
}
}Names, descriptions and schemas were written by the server and are shown as data.
Shared addresses on big platforms (Cloudflare, Vercel and the like) put unrelated servers together; those are marked shared_infrastructure. A match is a pivot, not a link between operators.