Remote MCP · Endpoint

MCP do Afiliado MCP server

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

UpLast checked 4 days ago

Server URL

https://mcpdoafiliado.com/mcp

The last check completed an MCP handshake.

Registry name
com.mcpdoafiliado/mcp-do-afiliado
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
170 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Busca produto e gera link de afiliado da Shopee, Amazon, Mercado Livre, AliExpress e Magalu.
Listing
From the official MCP registry (active).
Recent checks of MCP do Afiliado
CheckedResultHandshake
4 days agoHandshake completed170 ms
4 days agoHandshake completed706 ms
5 days agoHandshake completed179 ms
7 days agoHandshake completed618 ms
8 days agoHandshake completed618 ms
9 days agoHandshake completed752 ms
10 days agoHandshake completed775 ms
11 days agoHandshake completed1.01 s
12 days agoHandshake completed351 ms
15 days agoCredentials required—
18 days agoCredentials required—
20 days agoCredentials required—
22 days agoCredentials required—
24 days agoCredentials required—

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

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 MCP do Afiliado and makes no claim about it beyond what these checks measured.