Skip to content

MCP servers › io.github.CssEoCAO › bot-do-afiliado

MCP server · registry snapshot 2026-10-28 · last tested 2026-10-28

io.github.CssEoCAO/bot-do-afiliado

by CssEoCAO · GitHub account (the registry's namespace rule)Website ↗

Affiliate links, product search and offer posts for Shopee, Mercado Livre, Amazon and AliExpress. — the publisher's description

1 of 2 record checks metRead-only · tools listed 2026-10-28version 1.0.0streamable HTTP30 tools

Summary

io.github.CssEoCAO/bot-do-afiliado is a remote MCP server listed in the official MCP registry at version 1.0.0, under the namespace of the GitHub account CssEoCAO. On 2026-10-28 ProtocolProbe connected to it in read-only mode and read its inventory: 30 tools, 0 resources and 0 prompts.

Record checks

1 of 2 record checks met · 7 do not apply

  • met: Registry entry is active and says how to run it
  • not met: Source repository link opens
  • not applicable: Repository is not archived
  • not applicable: Code pushed to the repository in the 90 days before our check
  • not applicable: Repository publishes a security policy (SECURITY.md)
  • not applicable: Package names its licence with a standard (SPDX) identifier
  • not applicable: The version the registry lists can be installed and is not withdrawn
  • not applicable: npm package carries build provenance (attestation)
  • not applicable: No known critical or high advisory in the package or its dependencies
  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: no public GitHub repository

From public records, not a safety rating. Each check with its reason

Operate this server? Correct a fact · README badge · Run the checks yourself

Key facts

Runs
remote (hosted by the publisher)
Transport
streamable HTTP
Your own values
none declared (not a guarantee)
Sign-in
none needed to open a session
Tools
30
Last tested
2026-10-28

Tool list size

18,010 tokens on Claude Opus 5.5

Added to every request that loads this server's tools (30 tools). Counted with Anthropic's token counter on 2026-10-28, from the tool list we read on 2026-10-28. Median across 23,424 counted servers: 2,725 tokens. How it is counted

How a client gets in

Connects without signing in

Read from the server's public metadata on 2026-10-28 (app.botdoafiliado.com), in our read-only connection; no tool was called. It may have changed since. How it is read

Tool list at the three APIs

Not sent yet for this version (1.0.0).

Add to your client

Observed fact

This server accepted a session without any credential and lists 9 tools whose name or declaration suggests they change data (add_coupon, remove_coupon, set_template, set_userbot_config, add_showcase_item and 4 more). That is our reading of the names; we did not call them. Source: our connection, 2026-10-28.

How fresh this is

Live-tested
yes, a real session (not a text-only review)
Last tested
2026-10-28
Mode
read-only (no tool calls)
Latest version
1.0.0, published 2026-10-28 (registry, as of the 2026-10-28 snapshot)
First listed version
2026-10-28 (earliest version still in the registry; older removed versions would be earlier)
Registry data
snapshot 2026-10-28
Package and repository
checked 2026-10-28
Engine
mcp-runtime-engine@0.1.0 · sdk@1.32.0

Dead or stale signals

None found in the records we hold

Looked for and not found: deprecated in the registry. Does not apply: listed version cannot be installed or is withdrawn; repository link does not open; repository archived; no push in over 365 days. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.

Changes since the last refresh

New in the registry: not in the list of 2026-10-27, listed on 2026-10-28 with version 1.0.0 (published 2026-10-28).

Source: the official MCP Registry list on 2026-10-27 and on 2026-10-28.

What it is

What does this server offer?

Observed inventory
30tools
0resources
0prompts

None of its 30 tools are described as changing anything. For 30 the reading was uncertain, so no mark is shown.

  • convert_links

    “Converte um ou vários links (URLs de produtos/lojas) em links de afiliado do seu bot.”

    Publisher declares: read-only yes · destructive no · open-world yes

    3 inputs
    • urlstring“Um único link a converter (URL completa, com https://).”
    • urlsarray“Vários links a converter (até 150 por chamada; para mais, divida em lotes).”
    • telegram_user_idinteger“Opcional.”
  • “Retorna dados do produto (título, preço como número na moeda de "currency", imagem), o link de afiliado (affiliate_url), o link final (final_url) e o histórico de preços a partir de uma URL.”

    Publisher declares: read-only yes · destructive no · open-world yes

    3 inputs, 1 required
    • urlstringrequired“URL do produto.”
    • history_limitinteger“Opcional.”
    • watermarkboolean“Opcional.”
  • create_offer_post

    “Monta um post de oferta pronto para publicar (título, preço, cupom e link final) a partir de uma ou mais URLs de produto, usando o template de oferta do bot.”

    Publisher declares: read-only yes · destructive no · open-world yes

    5 inputs
    • urlstring“URL de um produto.”
    • urlsarray“Várias URLs de produto (até 20).”
    • couponstring“Opcional.”
    • ctastring“Opcional.”
    • telegram_user_idinteger“Opcional.”
  • search_productson 265 other servers

    “Busca produtos por palavra-chave nas APIs dos marketplaces do bot (Shopee, AliExpress, Amazon; Kabum e Magalu quando informados em "site").”

    Publisher declares: read-only yes · destructive no · open-world yes

    11 inputs, 1 required
    • querystringrequired“Palavra-chave / título a buscar.”
    • sitestring“Marketplace a consultar.”
    • limitinteger“Máximo de resultados (1 a 50; padrão 20).”
    • price_minnumber“Preço mínimo (na moeda do site, geralmente BRL).”
    • price_maxnumber“Preço máximo (na moeda do site, geralmente BRL).”
    • commission_minnumber“Comissão mínima, em fração (0.05 = 5%).”
    • official_onlyboolean“Se true, retorna só lojas oficiais (Shopee Mall / AliExpress TMALL).”
    • key_seller_onlyboolean“Se true, filtra apenas "key sellers" da Shopee — vendedores de alto desempenho selecionados pela própria plataforma.”
    • sortstring“Ordenação: relevance (padrão), price_asc (mais barato), price_desc (mais caro), commission_desc (maior comissão de afiliado), sales_desc (mais vendidos), ratin…”
    • pageinteger“Página de resultados (padrão 1) — use para ver mais itens.”
    • site_filtersobject“Filtros ESPECÍFICOS do marketplace (use só com "site" fixado).”
  • “Executa um comando/gatilho do bot — o MESMO executor do Telegram — e devolve o conteúdo pronto, aplicando o template do bot (TEXTO formatado, não JSON).”

    Publisher declares: read-only yes · destructive no · open-world yes

    7 inputs, 1 required
    • commandstringrequired“Comando/gatilho do bot.”
    • urlstring“Um link (quando o comando age sobre um produto/loja).”
    • urlsarray“Vários links (até 20; para lotes maiores de conversão, use convert_links).”
    • textstring“Texto livre (termo de busca ou a mensagem do comando).”
    • couponstring“Cupom (para os comandos oferta/cupom).”
    • ctastring“Opcional.”
    • telegram_user_idinteger“Opcional.”
  • “Lista os cupons cadastrados no bot (código, descrição, link, validade e os campos detalhados do desconto: discountType, discountValue, minPurchase, maxDiscount, isCashback e isSoldOut).”

    Publisher declares: read-only yes · destructive no · open-world no

    6 inputs
    • site_idinteger“Opcional.”
    • sitestring“Opcional.”
    • qstring“Filtro por código, descrição ou URL (opcional).”
    • limitinteger“Máximo de cupons (1 a 200; padrão 50).”
    • offsetinteger“Deslocamento para paginação (0 = início).”
    • statusstring“Filtro de status: "active" (padrão, só vigentes), "expired" (expirados por data — úteis para reativar com activate_coupon) ou "all" (todos).”
  • list_coupon_categories

    “Lista os sites de cupons do bot (id, nome e domínio).”

    Publisher declares: read-only yes · destructive no · open-world no

    2 inputs
    • querystring“Opcional.”
    • limitinteger“Opcional.”
  • add_coupon

    “Cadastra (ou atualiza) cupons no bot.”

    Publisher declares: read-only no · destructive no · idempotent yes · open-world no

    16 inputs
    • codestring“Código do cupom (ex.: BLACK10).”
    • sitestring“Loja ou marketplace do cupom (ex.: Shopee).”
    • site_idinteger“ID do site obtido em list_coupon_categories.”
    • descriptionstring“Descrição/condições do cupom.”
    • urlstring“Link do cupom.”
    • discount_typestring“Opcional.”
    • discount_valuenumber“Opcional.”
    • min_purchasenumber“Opcional.”
    • max_discountnumber“Opcional.”
    • is_cashbackboolean“Opcional.”
    • is_sold_outboolean“Opcional.”
    • convert_urlboolean“Se true, converte a "url" em link de afiliado antes de cadastrar.”
    • expires_atstring“Validade.”
    • starts_atstring“Início de vigência — data ISO ou epoch.”
    • raw_textstring“Opcional.”
    • couponsarray“Lote de cupons (até 50), cada um com code OU url e os demais campos.”
  • remove_coupon

    “Remove um cupom do bot pelo "id" (obtido em list_coupons) ou pelo "code".”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    2 inputs
    • idinteger“ID do cupom (vindo de list_coupons).”
    • codestring“Código do cupom (alternativa ao id).”
  • activate_coupon

    “Reativa um cupom expirado/inativo (de list_coupons com status="expired"), deixando-o vigente de novo.”

    Publisher declares: read-only no · destructive no · idempotent yes · open-world no

    3 inputs
    • idinteger“ID do cupom (vindo de list_coupons).”
    • codestring“Código do cupom (alternativa ao id).”
    • expires_atstring“Opcional.”
  • “Lê os templates do bot — tanto o FORMATO das ofertas (oferta, cupom, rodapé e rodapé por marketplace) quanto as mensagens de RESPOSTA (boas-vindas, uso de comando, carregando, sucesso, erro, entrega …”

    Publisher declares: read-only yes · destructive no · open-world no

    2 inputs
    • keystring“Opcional.”
    • keys_onlyboolean“Se true, lista só as chaves (sem o texto) — use para descobrir o que existe antes de ler/editar.”
  • set_template

    “Cria/atualiza (SOBRESCREVE) um template do bot.”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    3 inputs, 2 required
    • keystringrequired“Chave do template.”
    • textstringrequired“Texto do template (HTML do Telegram), com as variáveis entre chaves.”
    • modestring“Modo de formatação.”
Show 18 more tools
  • get_bot_infoon 1 other server

    “Mostra o que ESTE bot suporta: marketplaces com busca ativa (search_sites, usados por search_products), catálogos públicos (Kabum/Magalu, com flag de monetização), redes/domínios com conversão de lin…”

    Publisher declares: read-only yes · destructive no · open-world no

    Takes no inputs.

  • get_userbot_config

    “Mostra a configuração do módulo Puxador deste bot: settings (grupo de aprovação, destino padrão, blocklist global, fonte padrão de texto/foto, publicação automática na Vitrine, status da sessão, apro…”

    Publisher declares: read-only yes · destructive no · open-world no

    Takes no inputs.

  • set_userbot_config

    “Altera a configuração do módulo Puxador.”

    Publisher declares: read-only no · destructive yes · open-world no

    5 inputs
    • settingsobject“Settings do módulo (parcial).”
    • channelobject“Canal monitorado (cria ou atualiza pelo channelId).”
    • ruleobject“Regra de roteamento (cria, ou atualiza se mandar id).”
    • deleteChannelIdinteger“ID do canal monitorado a apagar (de get_userbot_config).”
    • deleteRuleIdinteger“ID da regra de roteamento a apagar (de get_userbot_config).”
  • get_userbot_history

    “Últimas ofertas capturadas pelo Puxador, com o texto CRU que chegou do canal e o texto FINAL depois das regras e da conversão de links (antes → depois), status, destino e quem decidiu.”

    Publisher declares: read-only yes · destructive no · open-world no

    5 inputs
    • limitinteger“Quantas (1 a 100; padrão 20).”
    • offsetinteger“Quantas pular (0 = as mais recentes).”
    • channelIdstring“Filtrar por canal-fonte.”
    • statusstring“Filtrar por status (PENDING, APPROVED, REJECTED, DISCARDED, ...).”
    • autoboolean“Só o que a aprovação automática publicou.”
  • preview_userbot_rules

    “Aplica um perfil de texto + substituições/bloqueios a um texto de exemplo e devolve o resultado, SEM salvar nada.”

    Publisher declares: read-only yes · destructive no · open-world no

    2 inputs, 1 required
    • textstringrequired“Texto de exemplo (o cru que chegaria do canal).”
    • rulesobject“Regras a testar: { converter, replacements, discardIfContains }.”
  • list_campaignson 37 other servers

    “Lista as campanhas de captação do workspace (Telegram e WhatsApp) com total de grupos, grupos abertos (com vaga e saudáveis), membros e link público.”

    Publisher declares: read-only yes · destructive no · open-world no

    3 inputs
    • statusstring“Filtro: "ativas" (padrão), "arquivadas" ou "todas".”
    • canalstring“Opcional.”
    • limiteinteger“Máximo de campanhas (1 a 100; padrão 50).”
  • “Detalhe de uma campanha (por id ou slug) com os grupos e o resumo dos últimos 7 e 30 dias: cliques, entradas, saídas, retenção, vendas e comissão.”

    Publisher declares: read-only yes · destructive no · open-world no

    1 input, 1 required
    • id_ou_slugstringrequired“ID da campanha (cmp_…) ou o slug do link personalizado.”
  • campaign_metrics

    “Série temporal de uma campanha entre "de" e "ate": cliques, entradas, saídas, permanência (entradas − saídas acumulado) e churn (saídas/entradas) por dia (até 93 dias) ou por hora (até 7 dias).”

    Publisher declares: read-only yes · destructive no · open-world no

    4 inputs, 3 required
    • id_ou_slugstringrequired“ID da campanha (cmp_…) ou o slug do link personalizado.”
    • destringrequired“Início do período.”
    • atestringrequired“Fim do período.”
    • granularidadestring“"dia" (padrão; até 93 dias) ou "hora" (até 7 dias).”
  • list_whatsapp_groups

    “Grupos WhatsApp do workspace com membros, o máximo de pessoas (o da campanha), se está trancado para novos membros, se é destino, ativo, saúde, incidentes abertos e as campanhas vinculadas.”

    Publisher declares: read-only yes · destructive no · open-world no

    4 inputs
    • campanha_idstring“Opcional.”
    • so_com_problemaboolean“Se true, só grupos com problema: saúde ruim, inativo, lotado ou com incidente aberto.”
    • limiteinteger“Máximo de grupos (1 a 200; padrão 50).”
    • offsetinteger“Quantos itens pular (0 = início).”
  • activity_history

    “Linha do tempo (mais recente primeiro) do que aconteceu: entradas/saídas por grupo (agregadas por hora), alertas de queda, grupos registrados, números WhatsApp adicionados/removidos/caídos, campanhas…”

    Publisher declares: read-only yes · destructive no · open-world no

    6 inputs
    • tipostring“Opcional.”
    • campanha_idstring“Opcional.”
    • destring“Opcional.”
    • atestring“Opcional.”
    • limiteinteger“Máximo de itens (1 a 200; padrão 50).”
    • offsetinteger“Quantos itens pular (0 = início).”
  • activity_stats

    “Totais do histórico de atividade por tipo e por ação no período (mesmos itens de activity_history).”

    Publisher declares: read-only yes · destructive no · open-world no

    2 inputs, 2 required
    • destringrequired“Início do período.”
    • atestringrequired“Fim do período.”
  • list_showcase_itemson 1 other server

    “Itens da Vitrine do bot (a página pública de ofertas /v/<slug>), mais recentes primeiro, com id, título, link, preço, cupom, se está ativo e quando vence.”

    Publisher declares: read-only yes · destructive no · open-world no

    2 inputs
    • limitinteger“Itens por página (1 a 100; padrão 20).”
    • offsetinteger“Quantos itens pular (0 = início).”
  • add_showcase_item

    “Publica uma oferta na Vitrine do bot (página pública, visível para qualquer visitante).”

    Publisher declares: read-only no · destructive no · idempotent no · open-world yes

    9 inputs, 2 required
    • titlestringrequired“Título do produto.”
    • link_urlstringrequired“Link do produto ou o affiliate_url de search_products (https://...).”
    • image_urlstring“Opcional.”
    • pricestring“Opcional.”
    • old_pricestring“Opcional.”
    • couponstring“Opcional.”
    • hookstring“Opcional.”
    • expires_atstring“Opcional.”
    • destaqueboolean“Opcional.”
  • remove_showcase_item

    “Remove de vez um item da Vitrine pelo id (de list_showcase_items).”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    1 input, 1 required
    • idintegerrequired“Id do item (list_showcase_items).”
  • list_userbot_queue

    “Fila de aprovação do Puxador (ofertas capturadas dos canais-fonte esperando decisão), mais novas primeiro: texto que será publicado, preço, cupons, destinos e se pode aprovar ou rejeitar.”

    Publisher declares: read-only yes · destructive no · open-world no

    3 inputs
    • limitinteger“Ofertas por página (1 a 50; padrão 20).”
    • cursorinteger“Opcional.”
    • channel_idstring“Opcional.”
  • approve_userbot_offer

    “PUBLICA a oferta nos canais de destino (os "destinos" de list_userbot_queue), para todos os membros, e não dá para desfazer pelo MCP.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    3 inputs, 1 required
    • idintegerrequired“Id da oferta (list_userbot_queue).”
    • use_api_textboolean“Opcional.”
    • use_api_photoboolean“Opcional.”
  • reject_userbot_offer

    “Descarta a oferta da fila do Puxador (não publica).”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    1 input, 1 required
    • idintegerrequired“Id da oferta (list_userbot_queue).”
  • propose_offer_post

    “Põe uma oferta que você escreveu na fila de aprovação do Puxador.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world no

    1 input, 1 required
    • textstringrequired“Texto da oferta, puro (sem HTML): produto, preço, cupom e o link da loja ou o de afiliado.”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-28.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

No AI reading was available for this server's tools (the two runs did not agree, or the listing was not reviewed).

Counted from the listing

Parameters with a description
100% of 115
Tools with a description
100% of 30
Typical description length
442 characters

The tool set

Counted from the listing

Tools
30
Size of the list
about 13,319 tokens for an agent to load (characters ÷ 4)
Naming
30 of 30 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 0 of 30 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the remote endpoint (Streamable HTTP)

We connected to this URL on 2026-10-28 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste:
https://app.botdoafiliado.com/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
  "mcpServers": {
    "bot-do-afiliado": {
      "url": "https://app.botdoafiliado.com/mcp"
    }
  }
}
VS Code · .vscode/mcp.json
{
  "servers": {
    "bot-do-afiliado": {
      "type": "http",
      "url": "https://app.botdoafiliado.com/mcp"
    }
  }
}
VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"bot-do-afiliado","type":"http","url":"https://app.botdoafiliado.com/mcp"}'
Claude Code
claude mcp add --transport http bot-do-afiliado https://app.botdoafiliado.com/mcp
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
  "mcpServers": {
    "bot-do-afiliado": {
      "type": "streamableHttp",
      "url": "https://app.botdoafiliado.com/mcp",
      "disabled": false,
      "autoApprove": []
    }
  }
}
Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
  "mcpServers": {
    "bot-do-afiliado": {
      "httpUrl": "https://app.botdoafiliado.com/mcp"
    }
  }
}
OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.bot-do-afiliado]
url = "https://app.botdoafiliado.com/mcp"
Zed · Zed settings file (command: zed: open settings file)
{
  "context_servers": {
    "bot-do-afiliado": {
      "url": "https://app.botdoafiliado.com/mcp"
    }
  }
}
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url https://app.botdoafiliado.com/mcp --transport http
  • The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
  • Zed's docs we read on 2026-10-26 describe remote servers by URL and do not name the transport.
  • The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Does the registry listing match what we found?

Feature #6

The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.

Registry saysWe foundResultSource · date
Remote endpoint app.botdoafiliado.com/mcpSession openedmatchesour test · 2026-10-28
No credential declared as requiredOpened a session without any credentialmatchesour test · 2026-10-28

Choosing

Record checks

Public records · not a safety rating

1 of 2 record checks met · 7 do not apply

  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: no public GitHub repository
  • MetRegistry entry is active and says how to run itActive, with a package or a remote address.
  • Not metSource repository link opensThe registry entry gives no repository link.What changes this check: This check opens the repository link in the registry entry. GitHub's documentation describes changing a repository's visibility in its Settings, under Danger Zone, Change visibility. GitHub: setting repository visibility
  • Does not applyRepository is not archivedNo public GitHub repository to read.
  • Does not applyCode pushed to the repository in the 90 days before our checkNo public GitHub repository to read.
  • Does not applyRepository publishes a security policy (SECURITY.md)No public GitHub repository to read.
  • Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
  • Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
  • Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
  • Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-28. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating. How each check works · Leaderboards

Common questions about io.github.CssEoCAO/bot-do-afiliado

Answered from the data above

Who publishes io.github.CssEoCAO/bot-do-afiliado?

The registry ties the namespace io.github.CssEoCAO to the GitHub account CssEoCAO; only its owner can publish under it. These are facts from the registry and GitHub, not a rating.

Does io.github.CssEoCAO/bot-do-afiliado need an API key or sign-in?

It opened a session without any credential on 2026-10-28. The registry entry declares no required credential; no declaration is not a guarantee.

Has io.github.CssEoCAO/bot-do-afiliado been security tested?

Partly. 3 of the 15 checks that apply to it were exercised. It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security verdict is published before verification.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Open without sign-in

It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-10-28
  1. Inventory: exercised
  2. Hidden instructions: exercised
  3. Real execution: not run · our policy
  4. Secret leak: not run · nothing to check it against
  5. Internal addresses: not run · our policy
  6. Unconfirmed changes: not run · our policy
  7. Bad input: not run · our policy
  8. Model requests: not run · nothing to check it against
  9. Sensitive questions: not run · nothing to check it against
  10. Folder boundary: not run · our policy
  11. Log leaks: not run · nothing to check it against
  12. Hidden content: not run · nothing to check it against
  13. Fake assistant turns: not applicable
  14. Token passthrough: not applicable
  15. Token audience: not applicable
  16. Sign-in redirect: not run · our policy
  17. Consent handling: not testable from outside
  18. Sign-in metadata: exercised

3 exercised12 not run (reason given)3 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 3 of the 15 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.

Exercised · 3
  • 1Inventory
    tool-list
    Reads the declared tools, resources and prompts.exercised
  • 2Hidden instructions
    description-poisoning
    Looks for hidden instructions in tool descriptions.exercised
  • 18Sign-in metadata
    oauth-url-scheme
    Checks the published sign-in metadata for unsafe URLs.exercised
Not run, with the reason · 12
  • 3Real execution
    real-execution
    Calls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 4Secret leak
    canary-leak
    Plants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 5Internal addresses
    ssrf
    Checks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 6Unconfirmed changes
    write-without-confirmation
    Checks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 7Bad input
    error-handling
    Sends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 8Model requests
    sampling
    Checks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 9Sensitive questions
    elicitation-sensitive-data
    Checks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 10Folder boundary
    root-boundary
    Checks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 11Log leaks
    logging-side-channel
    Checks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 12Hidden content
    audience-hiding
    Checks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against
  • 16Sign-in redirect
    open-redirect
    Checks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy
  • 17Consent handling
    confused-deputy
    Checks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside
Does not apply to this server · 3
  • 13Fake assistant turns
    fake-assistant-turn
    Checks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable
  • 14Token passthrough
    token-passthrough
    Checks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable
  • 15Token audience
    token-audience-validation
    Checks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable

Source: our own test, 2026-10-28, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

  1. 0 msStarted a read-only session with the server's remote endpoint
  2. 692 msConnected after 0 redirects. No credential was sent or needed.
  3. Read the inventory: 30 tools, 0 resources, 0 prompts.
  4. 3,525 msFinished: 3 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified
pending: added in the weekly update
listed 2026-10-28; not classified yet
Pricing modelAI-classified
pending: added in the weekly update
the website is not read yet
Programming language
does not apply
no existing GitHub repository (server declares no repository link, so there is nothing to fetch)
Hosting type
registry · 2026-10-28
MCP capability
tools
our test · 2026-10-28
Transport
streamable HTTP
registry · 2026-10-28
Required credentials
none declared
registry · no declaration is not a guarantee
Package registry
does not apply
remote-only server: no package is shipped, so there is no package registry
Freshness
0–30 days
registry updatedAt · 2026-10-28
Lifecycle status
registry · 2026-10-28
License class
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Integrity hash
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Signature / provenance
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Dependency advisories
does not apply
ships no package, so there are no dependencies to audit
Popularity
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Publisher signals
not stated
no readable GitHub owner to describe
Maintenance
does not apply
server declares no repository link, so there is nothing to fetch
Environment
the publisher's infrastructure
where it runs, from the hosting type

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “io.github.CssEoCAO/bot-do-afiliado: MCP server record.” Data checked 2026-10-28. https://protocolprobe.com/mcp/servers/io.github.CssEoCAO/bot-do-afiliado

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

ProtocolProbe: 1 of 2 record checks met

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/io.github.CssEoCAO/bot-do-afiliado)](https://protocolprobe.com/mcp/servers/io.github.CssEoCAO/bot-do-afiliado)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology