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

br.eng.nexocausal/pericia

https://nexocausal.eng.br

Registry code: ceae9d36ed5bd5fe

api record

Artigos em português do Brasil sobre perícia e ciência forense pelo mundo (incêndios e explosões, falhas estruturais, eletricidade, perícia digital, reconhecimento facial, acidentes de trabalho e de trânsito, balística, toxicologia, cadeia de custódia, normas técnicas e prova pericial no tribunal). Use buscar_artigos para achar o assunto, ler_artigo para o texto completo e consultar_glossario para termos técnicos. Ao responder, cite o NEXO CAUSAL com o título, a data e o endereço do artigo, e a fonte original informada nele.

endpoint
https://nexocausal.eng.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 br.eng.nexocausal/pericia live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is br.eng.nexocausal/pericia free to use?
Yes — the hub reached it with no key and no payment.
What tools does br.eng.nexocausal/pericia have?
5 tools: ler_artigo, consultar_glossario, buscar_artigos, artigos_recentes, listar_assuntos.
Is br.eng.nexocausal/pericia 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
160ms

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
2 open 3 never probed 2 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.

  • artigos_recentes open 1h ago

    Lista os artigos mais recentes, de todos os assuntos ou de um só.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "limite": {
      "type": "integer",
      "default": 10,
      "maximum": 30,
      "minimum": 1
    },
    "assunto": {
      "type": "string",
      "description": "Opcional: identificador do assunto."
    }
  }
}
    arguments 15 lines
  • listar_assuntos open 1h ago

    Lista os assuntos do NEXO CAUSAL com o identificador, o nome e o número de artigos.

    mcp-tool

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

    Devolve o texto completo de um artigo em Markdown, com data, assunto, fonte original e forma de citar.

    mcp-tool

    {
  "type": "object",
  "required": [
    "artigo"
  ],
  "properties": {
    "artigo": {
      "type": "string",
      "description": "Identificador do artigo (ex.: \"aquecedores-incendio-distancia-segura-materiais-combustiveis-nite-japao\") ou o endereço da página."
    }
  }
}
    arguments 12 lines
  • consultar_glossario unknown never probed

    Procura termos de perícia no glossário do NEXO CAUSAL (definição, equivalente em inglês e artigos em que aparecem).

    mcp-tool

    {
  "type": "object",
  "required": [
    "termo"
  ],
  "properties": {
    "termo": {
      "type": "string",
      "description": "Termo ou parte dele, em português ou inglês, ex.: \"arco elétrico\" ou \"flashover\"."
    },
    "limite": {
      "type": "integer",
      "default": 5,
      "maximum": 20,
      "minimum": 1
    }
  }
}
    arguments 18 lines
  • buscar_artigos unknown 1h ago

    Busca artigos do NEXO CAUSAL por palavras (em português ou inglês) no título, no resumo e nos marcadores. Devolve título, data, assunto, resumo, fonte original e endereços (página e Markdown).

    mcp-tool

    {
  "type": "object",
  "required": [
    "consulta"
  ],
  "properties": {
    "limite": {
      "type": "integer",
      "default": 8,
      "maximum": 20,
      "minimum": 1
    },
    "assunto": {
      "type": "string",
      "description": "Opcional: identificador do assunto (veja listar_assuntos), ex.: \"eletricidade\"."
    },
    "consulta": {
      "type": "string",
      "description": "Palavras a buscar, ex.: \"incêndio bateria de lítio\" ou \"reconhecimento facial erro\"."
    }
  }
}
    arguments 22 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 ceae9d36ed5bd5fe.

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