Home / MCP registry index / io.github.mcp-dir/astrea-mcp

Astrea (Aurum)

io.github.mcp-dir/astrea-mcp in the official MCP registry. Endpoint https://api.mcp.ai/p_astrea. Source: github.com/mcp-dir/astrea-mcp.

The registry describes it as: Reporting and queries over Astrea (Aurum), Brazilian legal-practice software: cases per client, cale

We read its 42 tools on 2026-10-29. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code

claude mcp add --transport http astrea-mcp https://api.mcp.ai/p_astrea

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "astrea-mcp": {
      "url": "https://api.mcp.ai/p_astrea"
    }
  }
}

VS Code

code --add-mcp '{"name":"astrea-mcp","type":"http","url":"https://api.mcp.ai/p_astrea"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

Install lazaretto-guard

claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

astrea_conta astrea_processos_buscar astrea_processos_list astrea_processos_count astrea_processos_por_cliente astrea_processos_novos_por_mes astrea_clientes astrea_agenda_global astrea_agenda_por_cliente astrea_andamentos astrea_etiquetas astrea_financeiro_honorarios astrea_financeiro_despesas astrea_etiquetar_aplicar astrea_etiquetar_remover astrea_andamento_criar astrea_documento_upload astrea_modelos astrea_documento_gerar astrea_encerrar astrea_processo_editar astrea_processo_criar astrea_caso_criar astrea_tarefa_criar astrea_prazo_criar astrea_compromisso_criar astrea_responsaveis astrea_tarefa_editar astrea_tarefa_excluir astrea_tarefa_etiquetar_aplicar astrea_tarefa_etiquetar_remover astrea_compromisso_editar astrea_kanbans astrea_tarefas_listar astrea_tarefa_mover astrea_compromisso_excluir show_version report_bug connect toolkit_info marketplace authenticate

Run this server? Show the check in your README

The badge reflects the latest weekly read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-mcp-dir-astrea-mcp/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-mcp-dir-astrea-mcp)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.