MCP Juridico Brasil
PYPI · MCP-JURIDICO-BRASIL
Processos judiciais brasileiros via DataJud CNJ: consulta, andamentos, resumo e prazos em dias úteis
Available components
Last scanned (3 hours ago)
Scores higher than 91% of PyPI servers
Category Education and Research
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security99
- No malware found by supply-chain analysis.Pass
- Known CVEs were checked across the 41 of 42 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- Dependency health was assessed across the 41 of 42 dependencies we could resolve, so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to DeHor-Labs/mcp-juridico-brasil). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 135 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability65
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1815 tokens (~201/item across 9 items; 9 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management63
- Stability observed for 19 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +16
- Malware scan: unverified → pass ▲ security
- 30 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed pypi/mcp-juridico-brasil@0.1.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | DeHor-Labs/mcp-juridico-brasil |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/DeHor-Labs/mcp-juridico-brasil/.github/workflows/publish.yml@refs/tags/v0.1.0 |
| Rekor log index | 1911816964 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:8e8b64d2d78a19bce8c18340ef4785feccbfa3f5d749ad553212e26282ec01a8 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 41 packages
| Packages resolved | 41 |
|---|---|
| Stale | 6 |
| Tree resolution | Partial |
The dependency tree was only partially resolved, so these counts may be incomplete.
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
buscar_processo_por_numero Buscar Processo Por Numero ~192
Busca os dados de um processo judicial pelo número CNJ. Consulta a API pública DataJud (CNJ) e retorna metadados do processo, classe, assuntos, órgão julgador, partes e histórico de movimentações. Cobertura: 91 tribunais (STF, STJ, TST, TSE, STM, TRF1-6, TRTs, TJs estaduais, TREs e militares estaduais).
| Name | Type | Req | Description |
|---|---|---|---|
| numero_processo | string | yes | Número no formato CNJ (ex: '0001234-56.2023.8.26.0100') ou sem formatação (20 dígitos). |
| tribunal | – | – | Sigla do tribunal (ex: 'TJSP', 'TRF4', 'STJ'). Se omitida, o sistema tenta localizar o processo em todos os tribunais (operação mais lenta). |
Structured output declared, but exposes no named fields.
No examples provided.
calcular_proximo_prazo Calcular Proximo Prazo ~257
Calcula o próximo prazo processual em dias úteis com calendário forense. Implementa art. 219 (dias úteis), art. 224 (termo inicial no dia seguinte) e art. 220 CPC (suspensão no recesso forense 20/dez a 20/jan).
| Name | Type | Req | Description |
|---|---|---|---|
| data_intimacao_iso | – | – | Data de intimação/publicação em ISO 8601 (ex: '2025-01-15'). Se omitida, usa a data da última movimentação disponível no DataJud. |
| numero_processo | string | yes | Número no formato CNJ (NNNNNNN-DD.AAAA.J.TT.OOOO). |
| tipo_ato | – | – | Tipo do ato processual para selecionar prazo CPC (ex: 'Contestacao', 'Embargos de Declaracao'). Se omitido, usa prazo padrão de 15 dias úteis. |
| tribunal | string | yes | Sigla do tribunal (ex: 'TJSP', 'TRF1'). |
| uf | – | – | Sigla da UF para incluir feriados estaduais no cálculo (ex: 'SP', 'RJ', 'MG'). Se omitida, usa apenas feriados nacionais. |
Structured output declared, but exposes no named fields.
No examples provided.
confirmar_leitura_intimacao Confirmar Leitura Intimacao ~468
Confirma a leitura de uma intimação no Domicílio Judicial Eletrônico. ╔══════════════════════════════════════════════════════════════════╗ ║ AÇÃO DE ALTO RISCO - EFEITO JURÍDICO REAL E IRREVERSÍVEL ║ ║ ║ ║ Confirmar a leitura de uma intimação via API DJe: ║ ║ - Registra ciência oficial com timestamp no sistema do CNJ. ║ ║ - INICIA a contagem do prazo processual correspondente. ║ ║ - NÃO pode ser desfeito via API. ║ ╚══════════════════════════════════════════════════════════════════╝ GATE DE SEGURANÇA (duplo): Esta tool opera em modo dry-run (sem efeito) por padrão. Para executar com efeito jurídico real, ambas as condições abaixo devem ser satisfeitas: 1. confirmar=True deve ser passado explicitamente nesta chamada. 2. DJE_PERMITIR_CONFIRMACAO_LEITURA=true deve estar definida no ambiente. Se qualquer uma das condições falhar, a tool retorna uma simulação sem qualquer chamada à API DJe - completamente seguro. Credenciais necessárias (via variáveis de ambiente): DJE_CLIENT_ID - client_id OAuth2 DJE_CLIENT_SECRET - client_secret OAuth2 DJE_BEHALF_OF_CPF - CPF do responsável (auditoria) DJE_PERMITIR_CONFIRMACAO_LEITURA - deve ser 'true' para modo real
| Name | Type | Req | Description |
|---|---|---|---|
| confirmar | boolean | – | DEVE ser True para indicar que o operador está ciente do efeito jurídico e deseja prosseguir. False por padrão. Mesmo com True, a operação só é executada se DJE_PERMITIR_CONFIRMA… |
| id_intimacao | string | yes | ID único da intimação no DJe (obtido via listar_intimacoes). |
| numero_processo | string | yes | Número CNJ do processo (ex: '0001234-56.2023.8.26.0100'). |
Structured output declared, but exposes no named fields.
No examples provided.
listar_intimacoes Listar Intimacoes ~267
Lista comunicações processuais do Domicílio Judicial Eletrônico (DJe). Operação SOMENTE LEITURA - sem efeito jurídico. Retorna as intimações, citações e notificações recebidas no DJe para o CNPJ/CPF cadastrado via DJE_BEHALF_OF_CPF. Intimações em segredo de justiça têm o conteúdo suprimido; apenas metadados são exibidos. Credenciais necessárias (via variáveis de ambiente): DJE_CLIENT_ID - client_id do OAuth2 (GeCli/DJe) DJE_CLIENT_SECRET - client_secret do OAuth2 (GeCli/DJe) DJE_BEHALF_OF_CPF - CPF do responsável (auditoria CNJ)
| Name | Type | Req | Description |
|---|---|---|---|
| apenas_pendentes | boolean | – | Se True (padrão), retorna apenas comunicações ainda não confirmadas como lidas. |
| limite | integer | – | Número máximo de comunicações a retornar (padrão: 50). |
| numero_processo | – | – | Número CNJ para filtrar comunicações de um processo específico (ex: '0001234-56.2023.8.26.0100'). Se omitido, retorna todas as comunicações recentes. |
Structured output declared, but exposes no named fields.
No examples provided.
listar_movimentacoes Listar Movimentacoes ~114
Lista as movimentações mais recentes de um processo judicial. Retorna o histórico de andamentos com código TPU, nome e data/hora, ordenado do mais recente para o mais antigo.
| Name | Type | Req | Description |
|---|---|---|---|
| limite | integer | – | Número máximo de movimentações a retornar (padrão 20, max 50). |
| numero_processo | string | yes | Número no formato CNJ. |
| tribunal | string | yes | Sigla do tribunal (obrigatória nesta tool para evitar varredura de todos os índices). |
Structured output declared, but exposes no named fields.
No examples provided.
listar_processos_monitorados Listar Processos Monitorados ~49
Lista processos com snapshot em memória na sessão atual. Retorna os números de processos que tiveram snapshot salvo nesta sessão. Use o resource processo://{numero}/snapshot para ler os dados completos.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
listar_tribunais Listar Tribunais ~44
Lista todos os tribunais suportados pelo MCP (91 ao total). Retorna siglas que podem ser usadas no parâmetro 'tribunal' das demais tools.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
monitorar_processo Monitorar Processo ~122
Verifica se um processo teve atualização após a data informada. Implementação Fase 2: polling via DataJud (sem tempo real). Fase 3 substituirá por notificação push via provider comercial.
| Name | Type | Req | Description |
|---|---|---|---|
| desde_iso | string | yes | Data/hora de referência em formato ISO 8601 (ex: '2024-01-15T08:00:00'). |
| numero_processo | string | yes | Número no formato CNJ. |
| tribunal | string | yes | Sigla do tribunal (obrigatória para monitoramento). |
Structured output declared, but exposes no named fields.
No examples provided.
resumir_andamento Resumir Andamento ~106
Retorna dados estruturados de um processo para geração de resumo pelo LLM. Esta tool busca o processo no DataJud e devolve os dados formatados junto com instruções para que o modelo gere o resumo em linguagem natural. O processamento semântico (resumo) fica no modelo, não no MCP.
| Name | Type | Req | Description |
|---|---|---|---|
| numero_processo | string | yes | Número no formato CNJ. |
| tribunal | – | – | Sigla do tribunal. Se omitida, o sistema pesquisa em todos. |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the MCP Juridico Brasil server?
MCP Juridico Brasil runs locally as a PyPI package, launched with uvx mcp-juridico-brasil. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · mcp-juridico-brasil
claude mcp add dehor-labs-mcp-juridico-brasil -- uvx mcp-juridico-brasil
What is the MCP Juridico Brasil server?
MCP Juridico Brasil is listed in the public MCP registry as io.github.DeHor-Labs/mcp-juridico-brasil. Processos judiciais brasileiros via DataJud CNJ: consulta, andamentos, resumo e prazos em dias úteis. This page covers its PyPI package (mcp-juridico-brasil).
Is the MCP Juridico Brasil server safe to use?
MCP Juridico Brasil scores 88 out of 100 on VerifyMCP. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the MCP Juridico Brasil server expose?
MCP Juridico Brasil exposes 9 tools: buscar_processo_por_numero, listar_movimentacoes, resumir_andamento, monitorar_processo, calcular_proximo_prazo, and 4 more. Their descriptions and schemas cost roughly 1,619 tokens of context every time the server is loaded.
Is the MCP Juridico Brasil server still maintained?
MCP Juridico Brasil is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the MCP Juridico Brasil server under?
MCP Juridico Brasil declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.