PJECAUTION
Overview
From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.
Servidor MCP (Model Context Protocol) para integração com o sistema PJE (Processo Judicial Eletrônico) brasileiro, com suporte completo a certificados digitais A1 e A3.
🚀 Características
- ✅ Integração completa com PJE - Acesso total à API do PJE
- 🔐 Certificados Digitais - Suporte A1 (arquivo) e A3 (token/smartcard)
- 📋 Gestão de Processos - Liste, busque e acompanhe processos
- 🏛️ Dados Judiciais - Órgãos julgadores, classes e assuntos
- 🔍 Filtros Avançados - Busca com múltiplos critérios
- 🌐 Multi-tribunal - Funciona com qualquer tribunal PJE
- 🤖 Claude Desktop - Integração nativa com IA
📦 Instalação Rápida
git clone https://github.com/seu-usuario/pje-mcp-server.git cd pje-mcp-server npm install cp .env.example .env # Edite o arquivo .env com suas configurações npm run build
⚙️ Configuração
1. Configuração Básica (.env)
# URL do seu tribunal PJE_BASE_URL=https://pje.tjce.jus.br PJE_APP_NAME=pje-tjce-1g # Certificado Digital (escolha uma opção) # Opção 1: Arquivo PFX PJE_CERTIFICATE_PFX_PATH=C:\certificado.pfx PJE_CERTIFICATE_PFX_PASSWORD=senha123 # Opção 2: Windows Store PJE_CERTIFICATE_THUMBPRINT=abc123...
2. Claude Desktop (Windows)
Adicione ao arquivo %APPDATA%\Claude\claude_desktop_config.json:
{
"mcpServers": {
"pje": {
"command": "node",
"args": ["C:\\caminho\\para\\pje-mcp-server\\build\\index.js"]
}
}
}3. Claude Desktop (Mac/Linux)
Adicione ao arquivo ~/.config/claude/claude_desktop_config.json:
{
"mcpServers": {
"pje": {
"command": "node",
"args": ["/caminho/para/pje-mcp-server/build/index.js"]
}
}
}🎯 Uso com Claude
Após configurar, reinicie o Claude Desktop e use comandos naturais:
"Configure o PJE do TJCE" "Liste meus processos" "Busque o processo 1234567-89.2024.8.06.0001" "Mostre os órgãos julgadores" "Quais são minhas audiências esta semana?"
🔐 Certi
b9810bee1877OBSERVED · 2026-10-08Connect
Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control. Replace the environment placeholders with a token scoped to the least it needs.
claude mcp add pje-mcp-server --env PJE_CERTIFICATE_PASSWORD=${PJE_CERTIFICATE_PASSWORD} --env PJE_CERTIFICATE_PFX_PASSWORD=${PJE_CERTIFICATE_PFX_PASSWORD} --env PJE_CLIENT_SECRET=${PJE_CLIENT_SECRET} --env PJE_PASSWORD=${PJE_PASSWORD} -- npx -y [email protected]{
"mcpServers": {
"pje-mcp-server": {
"command": "npx",
"args": [
"-y",
"[email protected]"
],
"env": {
"PJE_CERTIFICATE_PASSWORD": "${PJE_CERTIFICATE_PASSWORD}",
"PJE_CERTIFICATE_PFX_PASSWORD": "${PJE_CERTIFICATE_PFX_PASSWORD}",
"PJE_CLIENT_SECRET": "${PJE_CLIENT_SECRET}",
"PJE_PASSWORD": "${PJE_PASSWORD}"
}
}
}
}Exposed tools (10)
10 read · 0 write · 0 destructive.
| Tool | Risk | Description |
|---|---|---|
pje_buscar_processo | read | Busca um processo específico por ID |
pje_configurar | read | Configura a conexão com o PJE |
pje_configurar_certificado | read | Configura autenticação por certificado digital |
pje_info_certificado | read | Mostra informações sobre o certificado configurado |
pje_listar_assuntos | read | Lista assuntos processuais |
pje_listar_certificados | read | Lista certificados digitais disponíveis no Windows |
pje_listar_classes | read | Lista classes processuais |
pje_listar_orgaos_julgadores | read | Lista órgãos julgadores |
pje_listar_processos | read | Lista processos com filtros opcionais |
pje_status | read | Verifica o status da configuração e conexão do PJE |
Trust audit
CAUTIONgrade B · trust 88/100 Install with care. The audit found things worth knowing before you trust its output.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | FAIL |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- none-observed
- Network
- declared (4 observation(s))
- Shell
- none-observed
- Dependencies
- not all pinned
- Secrets in source
- none-found
Findings (3)
rejectUnauthorized: false,
ciphers: 'HIGH:!aNULL:!MD5:!RC4',
@modelcontextprotocol/sdk, axios, body-parser, dotenv, ejs, express, multer, node-forge
Gates applied: no_behavioural_pass.
b9810bee1877full audit observations/trust-audit/mcp-server/chapirousia__pje.json · Report an issue / request a re-scanAudit history
Every audit this server has had. A grade with a past is a grade somebody is still checking.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-08 | b9810bee1877 | CAUTION | B | 88 | first audit |
Questions
What tools does PJE expose?
10 in total: 10 read-only, 0 that write, and 0 that can delete or overwrite. Every one is listed on this page with its risk.
Is PJE safe to connect to an agent?
With care. The audit graded it B (88/100) and found 3 things worth knowing before you trust this server, listed below with the exact line each was found on.
What credentials does PJE need?
It reads PJE_CERTIFICATE_PASSWORD, PJE_CERTIFICATE_PFX_PASSWORD, PJE_CLIENT_SECRET and PJE_PASSWORD from the environment. Give it a token scoped to the least it needs — an agent that can be talked into calling a tool can be talked into calling it with your credentials.
How does PJE run?
It speaks stdio, so it runs as a local process your client starts. It is published on npm as pje-mcp-server at 1.0.0.
How current is this page?
The grade is for one exact copy of the source (b9810bee1877), read on 2026-10-08. The repository is watched and re-audited when it changes.