_ registry / mcp streamable-http · checked 58m ago

eleicoes-2026-br

https://urnas2026.duckdns.org

Registry code: 93295b11d8a9d4e2

api record

Dados oficiais do TSE das eleições 2026 (1º e 2º turnos). Sem chave há uma cota grátis diária; com chave (Authorization: Bearer tse_...) as consultas usam créditos comprados em Lightning no site.

endpoint
https://urnas2026.duckdns.org/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 eleicoes-2026-br live?
Yes — it answered the hub's last check (checked 58m ago). It answered 100% of checks over the last 30 days.
Is eleicoes-2026-br free to use?
Not measured yet.
What tools does eleicoes-2026-br have?
5 tools: explorar, buscar_candidatos, valores_dimensao, saldo, detalhar_candidato.
Is eleicoes-2026-br 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
584ms

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
5 never probed 0 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.

  • explorar unknown never probed

    Tabela dinâmica sobre as eleições de 2026 (1º e 2º turno): agrega uma medida por uma dimensão nas linhas e, opcionalmente, outra nas colunas, com filtros. Use para rankings, comparações e cruzamentos (ex.: votos por partido em cada UF).

    mcp-tool

    {
      "type": "object",
      "required": [
        "linhas"
      ],
      "properties": {
        "busca": {
          "type": "string",
          "description": "Trecho do nome de urna do candidato."
        },
        "ordem": {
          "enum": [
            "desc",
            "asc",
            "nome"
          ],
          "type": "string"
        },
        "limite": {
          "type": "integer",
          "description": "Máximo de linhas (padrão 50, máx. 500)."
        },
        "linhas": {
          "enum": [
            "turno",
            "uf",
            "municipio",
            "cargo",
            "partido",
            "candidato",
            "situacao",
            "genero",
            "instrucao",
            "ocupacao",
            "cor_raca"
          ],
          "type": "string",
          "description": "Dimensão das linhas."
        },
        "medida": {
          "enum": [
            "votos",
            "candidatos",
            "eleitos",
            "patrimonio",
            "patrimonio_medio"
          ],
          "type": "string",
          "description": "O que somar/contar. Padrão: votos."
        },
        "colunas": {
          "enum": [
            "turno",
            "uf",
            "municipio",
            "cargo",
            "partido",
            "candidato",
            "situacao",
            "genero",
            "instrucao",
            "ocupacao",
            "cor_raca"
          ],
          "type": "string",
          "description": "Dimensão das colunas (opcional)."
        },
        "filtros": {
          "type": "object",
          "description": "Mapa dimensão -> lista de valores. Ex.: {\"turno\":[\"1\"],\"cargo\":[\"DEPUTADO FEDERAL\"],\"uf\":[\"SP\"]}",
          "additionalProperties": {
            "type": "array",
            "items": {
              "type": "string"
            }
          }
        }
      }
    }
    arguments 79 lines
  • buscar_candidatos unknown never probed

    Busca candidatos de 2026 por nome, UF, cargo, partido, situação ou turno. Retorna votos totais e o código (sq_candidato) para detalhar.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "uf": {
          "type": "string"
        },
        "nome": {
          "type": "string"
        },
        "cargo": {
          "type": "string"
        },
        "turno": {
          "type": "integer"
        },
        "limite": {
          "type": "integer"
        },
        "partido": {
          "type": "string"
        },
        "situacao": {
          "type": "string"
        }
      }
    }
    arguments 26 lines
  • valores_dimensao unknown never probed

    Lista os valores possíveis de uma dimensão (ex.: cargos, partidos, municípios de uma UF) para montar filtros.

    mcp-tool

    {
      "type": "object",
      "required": [
        "dimensao"
      ],
      "properties": {
        "uf": {
          "type": "string"
        },
        "dimensao": {
          "enum": [
            "turno",
            "uf",
            "municipio",
            "cargo",
            "partido",
            "candidato",
            "situacao",
            "genero",
            "instrucao",
            "ocupacao",
            "cor_raca"
          ],
          "type": "string"
        }
      }
    }
    arguments 27 lines
  • saldo unknown never probed

    Mostra o saldo de créditos da chave usada e a cota grátis. Sem custo.

    mcp-tool

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

    Ficha de um candidato: dados públicos, votos por município em cada turno e bens declarados.

    mcp-tool

    {
      "type": "object",
      "required": [
        "sq_candidato"
      ],
      "properties": {
        "sq_candidato": {
          "type": "string"
        }
      }
    }
    arguments 11 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 93295b11d8a9d4e2.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/93295b11d8a9d4e2/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/93295b11d8a9d4e2/badge.svg)](https://brick.blue/agent/93295b11d8a9d4e2?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.

_ also on duckdns.org 8 entries

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.