Skip to main content
Glama
Sign In
judikatura-mcp

judikatura-mcp

by marshall1727
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to judikatura-mcp

No user-submitted related servers found.

    Related Servers

    • tk-mcp

      pawelknorps
      A
      license
      A
      quality
      C
      maintenance
      Enables searching Polish Constitutional Tribunal judgments and rulings (with facet filters and sorting) and fetching the full HTML text of a given judgment directly from trybunal.gov.pl, without authentication.
      3
      Apache 2.0

    • SAOS MCP

      pawelojdowski
      A
      license
      A
      quality
      C
      maintenance
      Provides access to Polish court judgments from the SAOS database. Enables search and retrieval of judgments with full-text search, filtering, and detailed case information.
      3
      20 npm
      1
      Apache 2.0

    • nl-rechtspraak

      pipeworx-io
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables searching Dutch court decisions by court, legal domain, document type and decision-date range, then resolving any result's ECLI to its full original Dutch text, along with court, dates, procedure, rechtsgebied, formal relations to other ECLIs, and linked statute identifiers for chaining to wetten tools. Covers published case law (uitspraken en conclusies) rather than statutes, with keyless access via a hosted gateway or a local stdio server.
      446 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.8/5.0

    Scored across 11 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes: lookup tables (list_courts/list_keywords), online search (search_decisions), case-number lookup (find_by_case_number), date browsing (browse_published), full-text retrieval (get_decision), export, and cache operations. There is mild overlap among the several 'find decisions' tools and between cache_fill and cache_fill_day, but descriptions make the intended boundary clear.

    Naming Consistency4/5

    Names follow a predictable snake_case convention, mostly verb_noun (list_courts, search_decisions, get_decision, export_decision). The cache group uses a noun-prefixed namespace (cache_fill, cache_fill_day, cache_search, cache_stats), a minor deviation but logically grouped and readable.

    Tool Count5/5

    11 tools is well-scoped for a judicial-decisions server, covering discovery, retrieval, export, and offline cache workflow. Each tool earns its place with no filler.

    Completeness4/5

    The surface covers the full lifecycle of finding, retrieving, exporting, and caching decisions, including offline search and status. Minor gaps such as citation/related-decision lookup exist, but core workflows are covered without dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources