Skip to main content
Glama

Related Servers

Alternatives to datajud-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables querying public Brazilian court proceedings metadata and movements via the CNJ/DataJud API, covering multiple courts.
      4
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables 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.
      -
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables 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.
      MIT
    • F
      license
      A
      quality
      B
      maintenance
      Exposes Brazilian public data — postal codes (CEP), company registrations (CNPJ), CPF/CNPJ validation, banks, national holidays, municipalities, and DDD area codes — as MCP tools and resources, backed by BrasilAPI, ViaCEP, and IBGE with caching, fallback, and rate limiting. Any MCP client such as Claude Desktop or Claude Code can query and validate this reference and registration data through natural language or programmatic calls.
      1
      -
    • A
      license
      A
      quality
      A
      maintenance
      Connects AI assistants to Brazilian judicial data from DataJud CNJ and 91 courts, enabling process consultation, monitoring, and deadline calculation under the Civil Procedure Code.
      9
      95 PyPI
      120
      MIT

    TDQS

    A4.3/5.0

    Scored across 4 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues