Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Court Decisions Ukraine MCP

REMOTE · MCP.EDEPUTAT.COM

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

Available components

+4 this week 63 Trust /100

Last scanned (12 hours ago)

Scores higher than 45% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Education and Research

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security46
Transport & Reachability100
Schema Quality & AI Usability64
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 539 tokens (~89/item across 6 items; 6 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management53
  • Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (11)

  • TLS certificate
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (2)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 8 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 6 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://mcp.edeputat.com/court-decisions/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.edeputat.com CN=YE2,O=Let's Encrypt,C=US 3 Nov 2026 1 Feb 2027 ECDSA 256 ECDSA-SHA384 67c58393e9fe73336a052b4791caaef3bcd
SANs: mcp.edeputat.com
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.edeputat.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
edeputat.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.edeputat.com/court-decisions/mcp Verified 200
http (plaintext) http://mcp.edeputat.com/court-decisions/mcp Inconclusive 406
MCP tools · 6 exposed · ~539 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
court_category_stats ~154

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

NameTypeReqDescription
categorystring––
courtstring––
date_fromstring––
date_tostring––
group_bystring––
limitinteger––

No output schema declared.

No examples provided.

get_decision ~46

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

NameTypeReqDescription
doc_id–yes–

No output schema declared.

No examples provided.

list_courts ~48

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

NameTypeReqDescription
limitinteger––
namestring––
regionstring––

No output schema declared.

No examples provided.

search_by_case_number ~127

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

NameTypeReqDescription
case_numberstringyes–
limitinteger––
prefixboolean––

No output schema declared.

No examples provided.

search_decisions ~131

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

NameTypeReqDescription
courtstring––
date_fromstring––
date_tostring––
justice_kindstring––
limitinteger––
querystring––

No output schema declared.

No examples provided.

stats ~33

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the Court Decisions Ukraine MCP server?

Court Decisions Ukraine MCP is a hosted endpoint at https://mcp.edeputat.com/court-decisions/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · mcp.edeputat.com

# add to Claude Code
claude mcp add --transport http ukraine-territorial-mcp-court-decisions 'https://mcp.edeputat.com/court-decisions/mcp'
Common questions

What is the Court Decisions Ukraine MCP server?

Court Decisions Ukraine MCP is listed in the public MCP registry as io.github.Ukraine-Territorial-MCP/court-decisions. Experimental read-only MCP over metadata of Ukrainian court decisions (DSA/EDRSR open data). This page covers its hosted endpoint (https://mcp.edeputat.com/court-decisions/mcp).

Is the Court Decisions Ukraine MCP server safe to use?

Court Decisions Ukraine MCP scores 63 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Court Decisions Ukraine MCP server expose?

Court Decisions Ukraine MCP exposes 6 tools: search_decisions, get_decision, list_courts, search_by_case_number, court_category_stats, stats. Their descriptions and schemas cost roughly 539 tokens of context every time the server is loaded.

Does the Court Decisions Ukraine MCP server require authentication?

No. We connected to Court Decisions Ukraine MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Court Decisions Ukraine MCP server still maintained?

Court Decisions Ukraine MCP is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Court Decisions Ukraine MCP server?

VerifyMCP ran 11 checks on Court Decisions Ukraine MCP, covering TLS certificate, HSTS header, DNSSEC, Transport and 7 more. 2 items could not be completed, a gap on our side rather than a finding about Court Decisions Ukraine MCP: Authorization and HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.