Remote MCP · Endpoint
Easyparser — Amazon Product & Seller Data MCP server
No. Easyparser — Amazon Product & Seller Data answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://mcp.easyparser.com/mcp
The last check completed an MCP handshake.
- Registry name
- com.easyparser/easyparser
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 337 ms
- Tools exposed
- 17 tools
- Uptime, last 30 days
- 100% from 19 checks
- Described by its publisher as
- Real-time Amazon product, seller, and search data for AI agents across 21 marketplaces.
- Website
- https://easyparser.com/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 337 ms |
| 18 hours ago | Handshake completed | 384 ms |
| 2 days ago | Handshake completed | 338 ms |
| 3 days ago | Handshake completed | 346 ms |
| 4 days ago | Handshake completed | 355 ms |
| 5 days ago | Handshake completed | 327 ms |
| 6 days ago | Handshake completed | 364 ms |
| 7 days ago | Handshake completed | 412 ms |
| 10 days ago | Handshake completed | 545 ms |
| 13 days ago | Handshake completed | 501 ms |
| 15 days ago | Handshake completed | 329 ms |
| 17 days ago | Handshake completed | 360 ms |
| 19 days ago | Handshake completed | 345 ms |
| 21 days ago | Handshake completed | 354 ms |
| 23 days ago | Handshake completed | 477 ms |
| 25 days ago | Handshake completed | 340 ms |
| 27 days ago | Handshake completed | 384 ms |
| 28 days ago | Handshake completed | 530 ms |
| 29 days ago | Handshake completed | 328 ms |
The last 19 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 Easyparser — Amazon Product & Seller Data and makes no claim about it beyond what these checks measured.