Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Pixel do Afiliado

REMOTE · APP.PIXELDOAFILIADO.COM

Meta Ads tracking for Shopee affiliates: campaigns, sales, commissions, ROAS and CAPI status.

+3 this week 83 Trust /100

Last scanned (5 hours ago)

Scores higher than 87% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Marketing and SEO

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security97
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
  • The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
Schema Quality & AI Usability71
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 2526 tokens (~140/item across 18 items; 18 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 19 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 4 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

  • 2 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 30 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 29 Oct 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 28 Oct 26 80

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Probed https://app.pixeldoafiliado.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=app.pixeldoafiliado.com CN=WE1,O=Google Trust Services,C=US 5 Oct 2026 3 Jan 2027 ECDSA 256 ECDSA-SHA256 9921020d89e66568133ef0ec870cfcb3
SANs: app.pixeldoafiliado.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of app.pixeldoafiliado.com. — Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
pixeldoafiliado.com. present 2371 13 Verified
app.pixeldoafiliado.com. Verified address RRset verified with the apex keys
Authentication Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result Enforced and verified
Enforced On tool calls
HTTP status 200

WWW-Authenticate challenge Bearer resource_metadata="https://app.pixeldoafiliado.com/.well-known/oauth-protected-resource"

Bearer resource_metadata="https://app.pixeldoafiliado.com/.well-known/oauth-protected-resource"
Header Value
strict-transport-security max-age=31536000; includeSubDomains
content-security-policy frame-ancestors 'none'; base-uri 'none'; form-action 'self'; object-src 'none'
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=(), payment=()

Protected resource metadata

Document https://app.pixeldoafiliado.com/.well-known/oauth-protected-resource
Retrieved Yes
Resource https://app.pixeldoafiliado.com/mcp
Authorisation server https://app.pixeldoafiliado.com/api/auth

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://app.pixeldoafiliado.com/mcp Verified 200
http (plaintext) http://app.pixeldoafiliado.com/mcp HTTPS enforced 301 https://app.pixeldoafiliado.com/mcp
MCP tools · 18 exposed · ~2,253 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
pixel_edit_campaign_url ~141

Atualiza os url_tags de um anúncio (ad) Meta — por exemplo para colocar os parâmetros do link rastreado. NÃO gera o link (isso é só no painel): recebe os url_tags prontos. DRY-RUN com dry_run:true. Requer plano Pro.

NameTypeReqDescription
ad_idstringyesID externo do anúncio (ad) Meta.
dry_runboolean–true ou ausente = DRY-RUN: descreve o efeito sem aplicar. false = EXECUTA a ação de fato. Só envie false após o usuário confirmar.
url_tagsstringyesNovos url_tags (query string de macros).

No output schema declared.

No examples provided.

pixel_get_campaign_status ~66

Detalha UMA campanha Meta a partir do cache: status efetivo, objetivo e orçamento diário (centavos de BRL). Informe o ID externo da campanha (descubra com pixel_get_campaigns).

NameTypeReqDescription
campaign_idstringyesID externo da campanha Meta (TEXT).

No output schema declared.

No examples provided.

pixel_get_campaigns ~103

Lista as campanhas Meta espelhadas no cache da conta (id externo, nome, status efetivo, objetivo e orçamento diário em centavos). Paginação: total/count/offset/has_more/next_offset.

NameTypeReqDescription
limitnumber–Máximo de campanhas (1–100, default 50).
offsetnumber–Deslocamento para paginação (default 0).
statusstring–Filtro de status (default all).

No output schema declared.

No examples provided.

pixel_get_capi_status ~51

Estado do envio de eventos ao Meta CAPI: contagem por status de entrega (sent/pending/failed) e os eventos mais recentes (event_id = conversionId garante dedup no Meta).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

pixel_get_commissions ~118

Comissão (centavos de BRL) no período quebrada por campanha Meta, com pedidos, itens, GMV, spend e ROAS (basis points). netCommission == totalCommission (afiliado direto).

NameTypeReqDescription
daysnumber–Janela em dias se start/end ausentes (1–366, default 30).
end_datestring–Fim (yyyy-mm-dd, UTC). Opcional (default hoje).
start_datestring–Início (yyyy-mm-dd, UTC). Opcional.

No output schema declared.

No examples provided.

pixel_get_conversions ~179

Lista SÓ as conversões com clique CASADO (atribuição completa: clique → venda), com campanha/adset/ad herdados do clique e o status de envio ao CAPI. Para a lista completa de vendas (inclusive sem clique), use pixel_get_shopee_sales. Paginação: total/count/offset/has_more.

NameTypeReqDescription
daysnumber–Janela em dias se start/end ausentes (1–366, default 30).
end_datestring–Fim (yyyy-mm-dd, UTC). Opcional (default hoje).
limitnumber–Máximo de conversões (1–200, default 50).
offsetnumber–Deslocamento para paginação (default 0).
start_datestring–Início (yyyy-mm-dd, UTC). Opcional.

No output schema declared.

No examples provided.

pixel_get_daily_trends ~128

Série temporal diária de uma métrica no período (para detectar tendências/anomalias). Métricas: commission, orders, clicks, spend (valores em centavos quando monetários).

NameTypeReqDescription
daysnumber–Janela em dias se start/end ausentes (1–366, default 30).
end_datestring–Fim (yyyy-mm-dd, UTC). Opcional (default hoje).
metricstring–Métrica da série (default commission).
start_datestring–Início (yyyy-mm-dd, UTC). Opcional.

No output schema declared.

No examples provided.

pixel_get_dashboard_summary ~121

Visão geral da conta no período: investimento (spend Meta), cliques rastreados, vendas Shopee, comissão, ROAS, EPC e taxa de conversão. Valores monetários em centavos de BRL.

NameTypeReqDescription
daysnumber–Janela em dias se start/end ausentes (1–366, default 30).
end_datestring–Fim (yyyy-mm-dd, UTC). Opcional (default hoje).
start_datestring–Início (yyyy-mm-dd, UTC). Opcional.

No output schema declared.

No examples provided.

pixel_get_links ~195

Lista os links rastreados da conta com o PRODUTO detectado de cada um. Por link: apelido (label), URL (https://…/r/{slug}), modo (edge=rastreado | static=estático), campanha/adset/ad associados, cliques (total + último) e o produto da Shopee (nome, imagem, preço em centavos, comissão em basis points, disponibilidade e quando foi checado). Filtros por status e campanha; paginação total/count/offset/has_more/next_offset.

NameTypeReqDescription
campaign_idstring–Filtra os links de uma campanha (metaCampaignId, modo estático). Opcional.
limitnumber–Máximo de links (1–100, default 50).
offsetnumber–Deslocamento para paginação (default 0).
statusstring–Filtro de status (default all).

No output schema declared.

No examples provided.

pixel_get_products_sold ~117

Lista os produtos vendidos no período (por productId): itens, pedidos, comissão e GMV em centavos. Útil para descobrir os itens que mais geram comissão a partir do tráfego pago.

NameTypeReqDescription
daysnumber–Janela em dias se start/end ausentes (1–366, default 30).
end_datestring–Fim (yyyy-mm-dd, UTC). Opcional (default hoje).
start_datestring–Início (yyyy-mm-dd, UTC). Opcional.

No output schema declared.

No examples provided.

pixel_get_roas ~145

Calcula o ROAS (comissão ÷ spend Meta) no período, por nível (campaign/adset/ad). Inclui spend, comissão, GMV (centavos), pedidos, cliques e derivadas em basis points. Base para escalar/pausar.

NameTypeReqDescription
daysnumber–Janela em dias se start/end ausentes (1–366, default 30).
end_datestring–Fim (yyyy-mm-dd, UTC). Opcional (default hoje).
levelstring–Nível de agregação (default campaign).
start_datestring–Início (yyyy-mm-dd, UTC). Opcional.

No output schema declared.

No examples provided.

pixel_get_shopee_sales ~180

Lista TODAS as vendas Shopee rastreadas do período (grão = item da conversão), inclusive as sem clique casado. Mostra status, GMV e comissão (centavos) e a atribuição (campaign/adset/ad) quando disponível. Paginação: total/count/offset/has_more/next_offset.

NameTypeReqDescription
daysnumber–Janela em dias se start/end ausentes (1–366, default 30).
end_datestring–Fim (yyyy-mm-dd, UTC). Opcional (default hoje).
limitnumber–Máximo de vendas (1–200, default 50).
offsetnumber–Deslocamento para paginação (default 0).
start_datestring–Início (yyyy-mm-dd, UTC). Opcional.

No output schema declared.

No examples provided.

pixel_pause_campaign ~105

Pausa uma campanha Meta (status PAUSED). DRY-RUN com dry_run:true (mostra o efeito sem aplicar); executa somente quando dry_run for false. Requer plano Pro para executar.

NameTypeReqDescription
campaign_idstringyesID externo da campanha Meta.
dry_runboolean–true ou ausente = DRY-RUN: descreve o efeito sem aplicar. false = EXECUTA a ação de fato. Só envie false após o usuário confirmar.

No output schema declared.

No examples provided.

pixel_push_capi ~109

Enfileira (ou reenfileira) os eventos Purchase/Refund elegíveis ao Meta CAPI da org. O dedup por event_id=conversionId garante idempotência (reenvio não duplica). DRY-RUN com dry_run:true. Requer plano Pro.

NameTypeReqDescription
dry_runboolean–true ou ausente = DRY-RUN: descreve o efeito sem aplicar. false = EXECUTA a ação de fato. Só envie false após o usuário confirmar.

No output schema declared.

No examples provided.

pixel_resume_campaign ~94

Reativa uma campanha Meta (status ACTIVE). DRY-RUN por padrão; executa só com dry_run:false. Requer plano Pro para executar.

NameTypeReqDescription
campaign_idstringyesID externo da campanha Meta.
dry_runboolean–true ou ausente = DRY-RUN: descreve o efeito sem aplicar. false = EXECUTA a ação de fato. Só envie false após o usuário confirmar.

No output schema declared.

No examples provided.

pixel_send_test_event ~117

Dispara um evento de teste ao Meta CAPI usando test_event_code (aparece em Test Events do Gerenciador de Eventos; NÃO afeta produção/otimização). Útil para validar a integração do Pixel/CAPI.

NameTypeReqDescription
event_namestring–Evento a simular (default Purchase).
test_event_codestringyesCódigo de teste do Gerenciador de Eventos (TESTxxxxx).
value_centsnumber–Valor (comissão) em CENTAVOS de BRL. Opcional.

No output schema declared.

No examples provided.

pixel_set_budget ~161

Altera o orçamento DIÁRIO de uma campanha (CBO) ou adset Meta. Valor em CENTAVOS de BRL (integer > 0). DRY-RUN por padrão; executa só com dry_run:false. Requer plano Pro.

NameTypeReqDescription
adset_idstring–ID do adset (use este OU campaign_id).
amount_centsnumberyesNovo orçamento diário em CENTAVOS de BRL (> 0).
campaign_idstring–ID da campanha (use este OU adset_id).
dry_runboolean–true ou ausente = DRY-RUN: descreve o efeito sem aplicar. false = EXECUTA a ação de fato. Só envie false após o usuário confirmar.

No output schema declared.

No examples provided.

pixel_trigger_sync ~123

Enfileira o pipeline de sincronização (pull Shopee → match → produto → insights Meta → push CAPI → agregação), o mesmo do "Sincronizar agora" do painel. ASSÍNCRONO: responde imediatamente e a cadeia roda em ~1–2 min; consulte pixel_get_dashboard_summary depois. Liberado a partir do plano Starter.

NameTypeReqDescription
dry_runboolean–true ou ausente = DRY-RUN: descreve o efeito sem aplicar. false = EXECUTA a ação de fato. Só envie false após o usuário confirmar.

No output schema declared.

No examples provided.

Install

How do I install the Pixel do Afiliado MCP server?

Pixel do Afiliado is a hosted endpoint at https://app.pixeldoafiliado.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · app.pixeldoafiliado.com

# add to Claude Code
claude mcp add --transport http csseocao-pixel-do-afiliado 'https://app.pixeldoafiliado.com/mcp'
Common questions

What is the Pixel do Afiliado MCP server?

Pixel do Afiliado is an MCP server listed in the public MCP registry as io.github.CssEoCAO/pixel-do-afiliado. Meta Ads tracking for Shopee affiliates: campaigns, sales, commissions, ROAS and CAPI status. This page covers its hosted endpoint (https://app.pixeldoafiliado.com/mcp).

Is the Pixel do Afiliado MCP server safe to use?

Pixel do Afiliado scores 83 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Pixel do Afiliado MCP server expose?

Pixel do Afiliado exposes 18 tools: pixel_get_dashboard_summary, pixel_get_campaigns, pixel_get_campaign_status, pixel_get_links, pixel_get_shopee_sales, and 13 more. Their descriptions and schemas cost roughly 2,253 tokens of context every time the server is loaded.

Does the Pixel do Afiliado MCP server require authentication?

Yes. Pixel do Afiliado asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the Pixel do Afiliado MCP server still maintained?

Pixel do Afiliado is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.