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

apipj

https://apipj.com.br

Registry code: 44c75e46960d314d

api record

Dados cadastrais públicos de CNPJ (Receita Federal, atualizados mensalmente). validar_cnpj e status_base são abertas; consultar_cnpj e buscar_cnpjs exigem uma chave de API da apipj no cabeçalho Authorization: Bearer (conta grátis em https://apipj.com.br/criar-conta) e consomem a cota mensal do plano (na busca, 1 por CNPJ devolvido). Limite por minuto e cota mensal seguem o plano da chave: Gratuito 10/min e 50.000/mês; Dev 30/min e 200.000/mês (R$ 12,90/mês); Pro 200/min e 600.000/mês (R$ 59,90/mês). Upgrade com checkout direto em https://apipj.com.br/painel?assinar=pro.

endpoint
https://apipj.com.br/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 apipj live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is apipj free to use?
Yes — the hub reached it with no key and no payment.
What tools does apipj have?
4 tools: validar_cnpj, buscar_cnpjs, consultar_cnpj, status_base.
Is apipj 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
671ms

last good check

priced tools
0

of 4 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 4 tools
1 open 3 never probed 1 of 4 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.

  • status_base open 1h ago

    Status do serviço e da base de CNPJ: mês do lote da Receita Federal carregado, data de geração e quantidade de CNPJs. Sem chave e sem consumo de cota.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • validar_cnpj unknown never probed

    Confere formato e dígitos verificadores de um CNPJ (numérico ou alfanumérico) sem consultar a base. Devolve cnpj, valido, formatado, alfanumerico e erro. Sem chave e sem consumo de cota.

    mcp-tool

    {
      "type": "object",
      "required": [
        "cnpj"
      ],
      "properties": {
        "cnpj": {
          "type": "string",
          "maxLength": 32,
          "minLength": 1,
          "description": "CNPJ com ou sem pontuação, numérico ou alfanumérico (ex.: 11.378.117/0001-20)"
        }
      },
      "additionalProperties": false
    }
    arguments 15 lines
  • buscar_cnpjs unknown 1h ago

    Lista estabelecimentos ativos da base da Receita Federal pela atividade econômica principal (CNAE, 7 dígitos) e/ou pelo município (código da Receita com 4 dígitos ou do IBGE com 7); pelo menos um dos dois filtros. Devolve {dataset_month, total, resultados, proximo_cursor}: cada resultado tem os dados cadastrais da consulta individual, sem o quadro de sócios. A página tem no máximo o limite por minuto do plano (ou o argumento limite, até esse valor) e cada CNPJ devolvido consome 1 da cota mensal e 1 do limite por minuto; a próxima página vem com cursor = proximo_cursor (null no fim). Exige chave de API da apipj.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "cnae": {
          "type": "string",
          "maxLength": 20,
          "minLength": 1,
          "description": "CNAE da atividade principal, 7 dígitos, com ou sem pontuação (ex.: 4781400 ou 47.81-4-00)"
        },
        "cursor": {
          "type": "string",
          "maxLength": 512,
          "minLength": 1,
          "description": "proximo_cursor da página anterior, com os mesmos filtros"
        },
        "limite": {
          "type": "integer",
          "maximum": 1000,
          "minimum": 1,
          "description": "Tamanho máximo da página, de 1 até o limite por minuto do plano (padrão: esse limite)"
        },
        "formato": {
          "enum": [
            "completo",
            "simplificado"
          ],
          "type": "string",
          "default": "completo",
          "description": "completo (padrão) ou simplificado, como em consultar_cnpj (sem sócios)"
        },
        "municipio": {
          "type": "string",
          "maxLength": 20,
          "minLength": 1,
          "description": "Código do município da Receita (4 dígitos, ex.: 7107 = São Paulo) ou do IBGE (7 dígitos, ex.: 3550308)"
        }
      },
      "additionalProperties": false
    }
    arguments 39 lines
  • consultar_cnpj unknown 1h ago

    Dados cadastrais públicos de um CNPJ na base da Receita Federal (lote mensal): razão social, nome fantasia, situação cadastral, endereço, telefones, e-mail, atividades CNAE, natureza jurídica, porte, capital social, Simples/MEI e sócios (CPF mascarado). Exige chave de API da apipj; cada consulta conta na cota mensal do plano. Limite por minuto e cota mensal seguem o plano da chave: Gratuito 10/min e 50.000/mês; Dev 30/min e 200.000/mês (R$ 12,90/mês); Pro 200/min e 600.000/mês (R$ 59,90/mês). Upgrade com checkout direto em https://apipj.com.br/painel?assinar=pro.

    mcp-tool

    {
      "type": "object",
      "required": [
        "cnpj"
      ],
      "properties": {
        "cnpj": {
          "type": "string",
          "maxLength": 32,
          "minLength": 1,
          "description": "CNPJ com ou sem pontuação, numérico ou alfanumérico (ex.: 11.378.117/0001-20)"
        },
        "formato": {
          "enum": [
            "completo",
            "simplificado"
          ],
          "type": "string",
          "default": "completo",
          "description": "completo (padrão: objetos aninhados, datas ISO e códigos da Receita) ou simplificado (plano, com datas DD/MM/AAAA e CNPJ, CEP e telefone formatados)"
        }
      },
      "additionalProperties": false
    }
    arguments 24 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 44c75e46960d314d.

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

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.