_ registry / mcp streamable-http · checked 2h ago

brindesbrasil

https://www.brindesbrasil.com.br

Registry code: 3540bd22c454be9d

api record

Catálogo da BrindesBrasil (brindesbrasil.com.br): brindes personalizados com a marca do cliente para empresas, eventos e feiras. Use buscar_produtos para achar itens, detalhes_produto para técnica de gravação e tabela de preço, calcular_preco para um orçamento por quantidade. Preços em reais, sem frete. Produção: 12 dias úteis após a aprovação e o pagamento. Não invente preços: use as ferramentas. Para fechar pedido, indique a página do produto ou https://www.brindesbrasil.com.br/contato/

endpoint
https://www.brindesbrasil.com.br/wp-json/bb/v1/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is brindesbrasil live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is brindesbrasil free to use?
Yes — the hub reached it with no key and no payment.
What tools does brindesbrasil have?
5 tools: detalhes_produto, indicar_similares, buscar_produtos, calcular_preco, listar_categorias.
Is brindesbrasil safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
460ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 5 tools
1 open 4 never probed 1 of 5 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • listar_categorias open 2h ago

    Lista as categorias principais do catálogo com slug, link, quantidade de produtos e subcategorias.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • detalhes_produto unknown never probed

    Detalhes de um produto: descrição, cores do mesmo modelo, estoque, medidas da caixa, técnicas de gravação disponíveis e tabela de preço por quantidade (preço unitário com 1 gravação).

    mcp-tool

    {
      "type": "object",
      "required": [
        "produto"
      ],
      "properties": {
        "produto": {
          "type": "string",
          "description": "SKU do produto (ex.: SPX-10338-BCO) ou ID numérico."
        }
      }
    }
    arguments 12 lines
  • indicar_similares unknown never probed

    Outras cores do mesmo modelo e produtos parecidos, na mesma ordem que a página do produto mostra.

    mcp-tool

    {
      "type": "object",
      "required": [
        "produto"
      ],
      "properties": {
        "limite": {
          "type": "integer",
          "default": 8,
          "maximum": 12,
          "minimum": 1
        },
        "produto": {
          "type": "string",
          "description": "SKU do produto (ex.: SPX-10338-BCO) ou ID numérico."
        }
      }
    }
    arguments 18 lines
  • buscar_produtos unknown 2h ago

    Busca brindes no catálogo por texto (nome, tipo, material) ou SKU. Devolve título, SKU, link, imagem, preço unitário a partir de (com gravação) e quantidade mínima.

    mcp-tool

    {
      "type": "object",
      "required": [
        "busca"
      ],
      "properties": {
        "busca": {
          "type": "string",
          "description": "O que procurar. Ex.: \"garrafa inox\", \"caneta metal touch\", \"SPX-08103\"."
        },
        "limite": {
          "type": "integer",
          "default": 8,
          "maximum": 10,
          "minimum": 1
        },
        "categoria": {
          "type": "string",
          "description": "Opcional: slug de categoria vindo de listar_categorias."
        }
      }
    }
    arguments 22 lines
  • calcular_preco unknown 2h ago

    Calcula preço unitário e total de um produto para uma quantidade e número de gravações (aplicações), com o mesmo motor do site. Não inclui frete.

    mcp-tool

    {
      "type": "object",
      "required": [
        "produto",
        "quantidade"
      ],
      "properties": {
        "produto": {
          "type": "string",
          "description": "SKU do produto (ex.: SPX-10338-BCO) ou ID numérico."
        },
        "aplicacoes": {
          "type": "integer",
          "default": 1,
          "maximum": 4,
          "minimum": 0,
          "description": "Número de gravações (0 = sem gravação, 1 a 4)."
        },
        "quantidade": {
          "type": "integer",
          "minimum": 1,
          "description": "Quantidade de peças."
        }
      }
    }
    arguments 25 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 3540bd22c454be9d.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/3540bd22c454be9d/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/3540bd22c454be9d/badge.svg)](https://brick.blue/agent/3540bd22c454be9d?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
90%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.