Remote MCP · Endpoint

Bot do Afiliado MCP server

No. Bot do Afiliado answered an MCP handshake 4 days ago.

UpLast checked 4 days 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
183 ms
Tools exposed
30 tools
Uptime, last 30 days
100% from 9 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).
Recent checks of Bot do Afiliado
CheckedResultHandshake
4 days agoHandshake completed183 ms
5 days agoHandshake completed383 ms
6 days agoHandshake completed200 ms
7 days agoHandshake completed216 ms
9 days agoHandshake completed309 ms
9 days agoHandshake completed176 ms
10 days agoHandshake completed193 ms
11 days agoHandshake completed166 ms
13 days agoHandshake completed768 ms

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

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.