Court Decisions Ukraine MCP

io.github.Ukraine-Territorial-MCPPublished by GitHub account Ukraine-Territorial-MCPv0.1.0Updated Nov 6, 2026

Experimental read-only MCP over metadata of Ukrainian court decisions (DSA/EDRSR open data).

VerifiedStreamable HTTPWeb executableKnowledge & MemoryData & Analytics

Overview

AI-generated overview

Read-only MCP server for searching metadata of Ukrainian court decisions from DSA/EDRSR open data, with court directories and statistics.

What you can do
  • Search decisions by keywords, court, proceeding type and date range, with a result limit
  • Fetch metadata for a single decision by its document ID
  • Look up courts by name or region
  • Retrieve all decisions for a case number, optionally matching by number prefix
  • Get decision counts grouped by court and/or category, plus overall database statistics
When to use it
Useful when you need to look up Ukrainian court decisions, trace a case by its number, or get counts and date ranges across courts and categories without opening the registry manually.
Requirements
Remote streamable HTTP endpoint; no package, account, API key or environment variable is declared. Network access to the endpoint is required.
Before you install
Read-only and experimental, so coverage and accuracy of the underlying open data are not guaranteed. Queries heavier than about five seconds are aborted with an error, so broad searches may fail.

Installation

In SourceWeft

  1. Open Court Decisions Ukraine MCP in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.Ukraine-Territorial-MCP%2Fcourt-decisions/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "court-decisions-ukraine": {
      "type": "http",
      "url": "https://mcp.edeputat.com/court-decisions/mcp"
    }
  }
}

Tools

6

search_decisions

Пошук рішень: query (слова: номер справи, суд, категорія, суддя; до 8 слів, до 200 символів), court (код або частина назви), justice_kind (код або назва виду провадження), date_from/date_to (YYYY-MM-DD, дата ухвалення), limit (1..50).

Parameterscourtlimitquerydate_todate_fromjustice_kind

get_decision

Метадані одного рішення за doc_id (ціле число, лише цифри 0-9). Поле judge — як у джерелі.

Parametersdoc_idrequired

list_courts

Довідник судів: name, region (частини назв), limit.

Parametersnamelimitregion

search_by_case_number

Усі рішення по справі за номером (нормалізація: пробіли, регістр, роздільники \ | /, лапки, №). prefix=true — пошук за початком номера (мін. 2 символи). Повертає метадані, суд, дату, вид, категорію, посилання на реєстр. limit 1..200 (за замовчуванням 50).

Parameterslimitprefixcase_numberrequired

court_category_stats

Кількість рішень за судом і/або категорією (за спаданням). Усі параметри необов'язкові: court і category — код або частина назви; date_from/date_to (YYYY-MM-DD, дата ухвалення); group_by = court | category | both; limit 1..200 (за замовчуванням 50). Надто важкий запит (>5 с) переривається з помилкою.

Parameterscourtlimitdate_tocategorygroup_bydate_from

stats

Загальна статистика бази: кількість, діапазон дат, розподіл за видами проваджень.

Takes no parameters.

Version history

1
  1. v0.1.0LatestNov 6, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.