Remote MCP · Endpoint
Bot do Afiliado MCP server
No. Bot do Afiliado answered an MCP handshake 3 hours ago.
UpLast checked 3 hours ago
Server URL
https://app.botdoafiliado.com/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.CssEoCAO/bot-do-afiliado
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 770 ms
- Tools exposed
- 31 tools
- Uptime, last 30 days
- 100% from 11 checks
- Described by its publisher as
- Affiliate links, product search and offer posts for Shopee, Mercado Livre, Amazon and AliExpress.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 3 hours ago | Handshake completed | 770 ms |
| 4 days ago | Handshake completed | 447 ms |
| 14 days ago | Handshake completed | 183 ms |
| 15 days ago | Handshake completed | 383 ms |
| 15 days ago | Handshake completed | 200 ms |
| 17 days ago | Handshake completed | 216 ms |
| 18 days ago | Handshake completed | 309 ms |
| 19 days ago | Handshake completed | 176 ms |
| 20 days ago | Handshake completed | 193 ms |
| 21 days ago | Handshake completed | 166 ms |
| 23 days ago | Handshake completed | 768 ms |
The last 11 checks. Full history is kept for 30 days; the all-time counter stands at 11 responding of 11.
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 Bot do Afiliado and makes no claim about it beyond what these checks measured.