datajud-mcp
Related Servers
Alternatives to datajud-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables Claude to look up Brazilian court cases in the CNJ public DataJud API by CNJ process number, automatically resolving the court and returning case metadata (class, subjects, judging body, degree, dates) and recent movements. Covers federal, state, and labor courts without logins or document access.MIT
- AlicenseNot gradedqualityCmaintenanceEnables querying public Brazilian court proceedings metadata and movements via the CNJ/DataJud API, covering multiple courts.4MIT
- AlicenseAqualityCmaintenanceEnables natural-language queries of Brazilian court cases through the public DataJud and DJEN APIs, retrieving case details, movements, publications, and parties across 92 tribunals, and calculating procedural deadlines in business days. It also offers optional Domicílio Judicial Eletrônico tools for listing and acknowledging intimations.11MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for querying Brazil's CNJ DataJud public API. Enables validating CNJ process numbers, searching lawsuits by number, and listing courts.MIT
- FlicenseNot gradedqualityCmaintenanceEnables querying Brazilian judicial case data through CNJ public APIs: fetching case metadata and movements via DataJud, searching publications and intimations from the national electronic justice gazette (DJEN) by case number or OAB, and downloading publication certificates as PDFs.-
- AlicenseNot gradedqualityBmaintenanceEnables searching Brazilian court jurisprudence directly in official sources (STF, STJ, TNU, TRF1–6, Turmas Recursais, TRUs, and BNP/CNJ qualified precedents), returning literal ementas, panel, rapporteur, dates, and full-text links. It works as an MCP server for Claude Code and Claude Desktop as well as a command-line tool, with parallel multi-court queries and source diagnostics.1MIT
TDQS
Scored across 4 tools
Each tool targets a distinct resource and action: fetching one case, listing movements for a case, listing courts, and searching cases. The boundaries are clear, and the descriptions reinforce when to use search_cases versus get_case or list_movements.
All tools use consistent snake_case verb_noun naming (get_case, list_movements, list_courts, search_cases). The verbs accurately reflect the operations and there are no mixed conventions.
Four tools are well-scoped for a focused court-data server and each earns its place: discovery, search, case retrieval, and movement retrieval. Nothing appears redundant or missing at the count level.
The surface covers the core lifecycle: discover courts, search cases, fetch case covers, and list movements with incremental updates via `since`. A minor gap is the lack of a tool to resolve CNJ TPU class/subject codes, which search_cases requires as numeric inputs.