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.

lahend.ee — Estonian court decisions

REMOTE · LAHEND.EE · 2 COMPONENTS · SCANNED SEP 20

Estonian court decisions: full-text case-law search, each ruling linked to its companies. Free.

0 this week 82 Trust /100
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 Security66
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • Authorisation not fully verified: no authorisation is required to call this server, and 20 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
Schema Quality & AI Usability78
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 2646 tokens (~132/item across 20 items; 20 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage94
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 79% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 20 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 21 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the lahend.ee — Estonian court decisions MCP server?

lahend.ee — Estonian court decisions is a hosted endpoint at https://lahend.ee/api/lahend-mcp/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 · lahend.ee

# add to Claude Code
claude mcp add --transport http nimistu-lahend-mcp 'https://lahend.ee/api/lahend-mcp/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "nimistu-lahend-mcp": {
      "url": "https://lahend.ee/api/lahend-mcp/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "nimistu-lahend-mcp": {
      "type": "http",
      "url": "https://lahend.ee/api/lahend-mcp/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.nimistu-lahend-mcp]
url = "https://lahend.ee/api/lahend-mcp/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "nimistu-lahend-mcp": {
      "type": "remote",
      "url": "https://lahend.ee/api/lahend-mcp/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add nimistu-lahend-mcp --url 'https://lahend.ee/api/lahend-mcp/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  nimistu-lahend-mcp:
    url: "https://lahend.ee/api/lahend-mcp/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "nimistu-lahend-mcp": {
      "Transport": "http",
      "Url": "https://lahend.ee/api/lahend-mcp/mcp"
    }
  }
}
# add to Vellum
assistant mcp add nimistu-lahend-mcp -t streamable-http -u 'https://lahend.ee/api/lahend-mcp/mcp'
// mcp.json
{
  "mcpServers": {
    "nimistu-lahend-mcp": {
      "type": "http",
      "url": "https://lahend.ee/api/lahend-mcp/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

  • 26 Aug 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Aug 26 0
    • Stability: 0.97 → pass security
  • 24 Aug 26 +1

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

  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 5 Aug 26 0
    • Tool “authority_documents_for_ruling” rewrote its description, which is the text the model reads security
    • Tool “list_categories” rewrote its description, which is the text the model reads security
    • Tool “search_rulings” rewrote its description, which is the text the model reads security
    • Schema quality: 120 → 132 functional
  • 31 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 29 Jul 26 0
    • HSTS header: unverified → pass security
    • Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 20 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
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 20 Sept 2026 · Probed https://lahend.ee/api/lahend-mcp/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=lahend.ee CN=WE1,O=Google Trust Services,C=US 16 Sept 2026 15 Dec 2026 ECDSA 256 ECDSA-SHA256 b3feeaae0e2d85d20e66a746ab011f3d
SANs: lahend.ee, *.lahend.ee
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of lahend.ee. Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
ee. present 34382 8 Verified
lahend.ee. present 2371 13 Verified
lahend.ee. Verified address RRset verified with the apex keys
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
Header Value
strict-transport-security max-age=31536000; includeSubDomains
x-content-type-options nosniff
referrer-policy strict-origin-when-cross-origin

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://lahend.ee/api/lahend-mcp/mcp Verified 200
http (plaintext) http://lahend.ee/api/lahend-mcp/mcp HTTPS enforced 308 https://lahend.ee/api/lahend-mcp/mcp
MCP tools · 20 exposed · ~2,386 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
authority_documents_for_ruling ~180

Given a ruling id, return documents from Estonian public-authority document registers that name the same companies - procurement files, licences, correspondence, inspections. A court dispute and an authority's file about the same company are the two halves nobody normally sees together. Sourced from dokumendiregister.ee. This depends on the ruling having a company linked to it, which holds for about 19% of the corpus: parties are extracted from the decision text by registry code, and a judgment that names a company without its code yields no link. An empty list therefore means either no linked company or no matching documents - it is not evidence that no authority holds a file.

NameTypeReqDescription
idstringyesRuling id, e.g. 'ruling:1279503'.
limitintegerMax documents (default 8).
NameTypeReqDescription
documentsarrayyes

No examples provided.

estonian_rulings_citing_eu_law ~127

Given a CELEX (an act like '32016R0679', or a Court of Justice judgment like '62014CJ0362'), return the Estonian court decisions that cite it. This is the join no other source publishes: EUR-Lex knows the EU instrument, Riigi Teataja knows the Estonian decision, and nobody connects them.

NameTypeReqDescription
articlestringOnly decisions citing this article of the act.
celexstringyesCELEX of an EU act or judgment.
limitinteger
NameTypeReqDescription
celexstringyes
rulingsarrayyes
totalRulingsnumberyes

No examples provided.

eu_act ~109

Fetch an EU regulation or directive by CELEX (e.g. '32016R0679' for the GDPR), article by article, in Estonian. Also reports how many Estonian court decisions cite it and which articles they lean on - the part EUR-Lex cannot answer.

NameTypeReqDescription
articlestringReturn only this article, e.g. '5'.
celexstringyesCELEX number, e.g. '32016R0679'. Sector 3 acts only.
NameTypeReqDescription
articleCountnumberyes
articlesarrayyes
celexstringyes
citingRulingsnumberyes
mostCitedArticlesarrayyes
titlestring|nullyes
urlstringyes

No examples provided.

eu_law_cited_by_ruling ~73

Given an Estonian ruling id (from `search`), list the EU instruments it cites - regulations, directives and Court of Justice judgments - with the articles named where the decision names them.

NameTypeReqDescription
idstringyesRuling id, e.g. 'ruling:1279503'.
NameTypeReqDescription
citedarrayyes

No examples provided.

eu_law_search ~109

Search EU regulations and directives, and Court of Justice / European Court of Human Rights judgments, by Estonian title or case number. The corpus is Estonian-language throughout: 94% of the Court of Justice's output is translated into Estonian, and essentially nothing indexes it in Estonian. Returns ids usable with eu_law_fetch.

NameTypeReqDescription
limitinteger
querystringyesEstonian title words, or a case number such as 'C-362/14'.
NameTypeReqDescription
resultsarrayyes

No examples provided.

fetch ~128

Retrieve the full text + metadata for any `id` returned by `search`. Handles all three kinds: `ruling:<n>` (a court decision with its linked companies), `law:<n>` (an act in its current redaktsioon, all paragraphs) and `section:<n>:<par>` (a single paragraph - prefer this over pulling a whole act). Returns Markdown plus the canonical lahend.ee URL.

NameTypeReqDescription
idstringyesTyped id from `search`: 'ruling:1279503', 'law:12345' or 'section:12345:199'.
NameTypeReqDescription
idstringyes
metadataobjectyes
textstringyesThe full decision rendered as Markdown.
titlestringyes
urlstringyes

No examples provided.

get_law_section ~221

Return a single § of an Estonian act, addressed the way lawyers cite it: an abbreviation and a number, e.g. abbrev='KarS', paragrahv='199', or abbrev='TsMS', paragrahv='430'. This is the precise way to answer a legal question - pulling a whole act costs thousands of tokens and buries the answer. Text comes from the act's current redaktsioon.

NameTypeReqDescription
abbrevstringyesAct abbreviation as cited: KarS, TsMS, VÕS, PankrS, RahaPTS…
paragrahvstringyesParagraph number, e.g. '199'. Superscript sections are addressed as '43-1' or '43¹' (§ 43¹) - these are DIFFERENT provisions from § 43. A full citation like '§ 430 lg 1' is also accepted; the lõige i…
NameTypeReqDescription
foundbooleanyes
textstring
titlestring
urlstring

No examples provided.

law_versions ~82

List an act's redaktsioonid (consolidated versions) with their validity ranges, newest first. Use this to answer 'what did this say on date X' - Estonian law is amended constantly and the current text is often not the one that applied to the facts.

NameTypeReqDescription
abbrevstringyesAct abbreviation, e.g. 'TsMS'.
NameTypeReqDescription
actstringyes
urlstringyes
versionsarrayyes

No examples provided.

list_categories ~97

All areas of law (asja_kategooria) present in the corpus, each with its ruling count. Use a category as the `category` filter in `search_rulings`. These counts do NOT sum to the corpus size: about 26% of rulings carry no category, so they appear in `list_courts` totals and in unfiltered search but in no category here. Filtering by category silently excludes them.

Input schema present but exposes no named parameters.

NameTypeReqDescription
categoriesarrayyes
corpusTotalnumberyes
uncategorisednumberyesRulings with no asja_kategooria - not reachable via the `category` filter.

No examples provided.

list_courts ~42

All Estonian courts that have published decisions, each with its ruling count. Use a court name as the `court` filter in `search_rulings`.

Input schema present but exposes no named parameters.

NameTypeReqDescription
courtsarrayyes

No examples provided.

most_cited_eu_law ~65

Ranked by how many Estonian decisions cite them. A good starting point for 'which EU law actually matters in Estonian practice' - the answer is concentrated in consumer protection, jurisdiction, asylum and agriculture rather than spread evenly.

NameTypeReqDescription
limitinteger
NameTypeReqDescription
instrumentsarrayyes

No examples provided.

most_cited_sections ~56

The statute paragraphs cited by the most court decisions, ranked. A map of where Estonian litigation actually happens, and a good starting point when exploring an unfamiliar area.

NameTypeReqDescription
limitintegerHow many (default 20).
NameTypeReqDescription
sectionsarrayyes

No examples provided.

recent_rulings ~35

The newest published rulings (by decision date), across all courts and areas of law.

NameTypeReqDescription
limitinteger
NameTypeReqDescription
rulingsarrayyes

No examples provided.

rulings_by_company ~108

Given an 8-digit Estonian registry code (registrikood), return every court decision that names that company, with its role (claimant/defendant/etc.) and the other parties. This company↔case-law join is unique to lahend.ee. Find a registry code via nimistu.ee or the nimistu MCP.

NameTypeReqDescription
limitinteger
reg_codestringyes8-digit Estonian company registry code, e.g. '16887028'.
NameTypeReqDescription
companyyes
countnumberyes
rulingsarrayyes

No examples provided.

rulings_citing_section ~161

Given an act abbreviation and a §, return the court decisions that actually cite it, newest first, with a total count. Built from 3.05M citations extracted from the decision texts themselves. This answers 'how have the courts applied KarS § 199' - the question statute text alone cannot answer, and the reason to use lahend.ee over reading Riigi Teataja.

NameTypeReqDescription
abbrevstringyesAct abbreviation as cited: KarS, TsMS, VÕS, PankrS…
limitintegerMax rulings returned (default 10).
paragrahvstringyesParagraph number, e.g. '199'. A full citation is accepted; the lõige is ignored.
NameTypeReqDescription
rulingsarrayyes
sectionstringyes
totalRulingsnumberyesHow many distinct rulings cite this §.

No examples provided.

search ~169

Full-text search across Estonian LAW - both court decisions (civil, administrative and criminal rulings) and legislation (acts and their individual paragraphs), from Riigi Teataja, indexed by lahend.ee. Inflection-tolerant; wrap a phrase in "quotes" for an exact match. Every result carries a stable typed `id` - `ruling:<n>`, `law:<n>` or `section:<n>:<par>` - which `fetch` resolves. Use this when you need the legal position on something and do not yet know whether the answer is in a statute or in case law.

NameTypeReqDescription
limitintegerMax results (default 10).
querystringyesLegal terms, a case number, a party/company name, or a "quoted phrase".
NameTypeReqDescription
resultsarrayyes
totalnumberyesTotal matching rulings.

No examples provided.

search_law_sections ~116

Full-text search across the paragraphs of every in-force Estonian act (4M+ sections). Answers 'which provision governs X' directly, returning the paragraphs themselves rather than acts you then have to read. Each hit carries a `section:` id for `fetch`.

NameTypeReqDescription
limitintegerMax results (default 8).
querystringyesA legal term or phrase, e.g. 'pankrotiavaldus', 'ehitusluba', 'töölepingu ülesütlemine'.
NameTypeReqDescription
resultsarrayyes

No examples provided.

search_laws ~108

Find Estonian acts by title or abbreviation (KarS, TsMS, VÕS…). Returns each act with a `law:` id for `fetch`, its type, issuer and whether it is still in force. Use get_law_section when you already know the paragraph you want.

NameTypeReqDescription
inForceOnlybooleanOnly acts currently in force (default true).
limitintegerMax results (default 10).
querystringyesTitle fragment or abbreviation.
NameTypeReqDescription
resultsarrayyes
totalnumberyes

No examples provided.

search_rulings ~307

Full-text ruling search with optional filters: court name, case type (civil/administrative/criminal), area of law (asja_kategooria) and a decision-date range. Returns a page of rulings with a total count. Use `list_courts` / `list_categories` to discover valid filter values. Two coverage limits worth knowing, because both are silent: - `companies` is populated on about 19% of rulings. Parties are extracted from the decision text by registry code, and many judgments name a company without ever stating its code. An EMPTY array means no code was found in the text, NOT that no company was involved. - About 26% of rulings carry no `asja_kategooria` at all, so filtering by `category` silently excludes them. Omit the filter to search the whole corpus.

NameTypeReqDescription
case_typestring
categorystringExact area of law, e.g. 'Võlaõigus'.
courtstringExact court name, e.g. 'Harju Maakohus Tallinna kohtumaja'.
date_fromstringYYYY-MM-DD lower bound (decision date).
date_tostringYYYY-MM-DD upper bound (decision date).
limitinteger
offsetinteger
querystringFree text (or "quoted phrase"); omit to browse by filters alone.
NameTypeReqDescription
rulingsarrayyes
totalnumberyes

No examples provided.

sections_cited_by_ruling ~93

Given a ruling id (from `search`), list the statute paragraphs it cites, with the lõiked named and each § resolved to its act. Use it to see the legal basis of a decision without reading the whole judgment, then `fetch` a `section:` id for the provision text.

NameTypeReqDescription
idstringyesRuling id, e.g. 'ruling:1279503'.
NameTypeReqDescription
sectionsarrayyes

No examples provided.

Common questions

What is the lahend.ee — Estonian court decisions MCP server?

lahend.ee — Estonian court decisions is an MCP server listed in the public MCP registry as io.github.Nimistu/lahend-mcp. Estonian court decisions: full-text case-law search, each ruling linked to its companies. Free. This page covers its hosted endpoint (https://lahend.ee/api/lahend-mcp/mcp).

Is the lahend.ee — Estonian court decisions MCP server safe to use?

lahend.ee — Estonian court decisions scores 82 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 lahend.ee — Estonian court decisions MCP server expose?

lahend.ee — Estonian court decisions exposes 20 tools: search, fetch, get_law_section, search_law_sections, search_laws, and 15 more. Their descriptions and schemas cost roughly 2,386 tokens of context every time the server is loaded.

Does the lahend.ee — Estonian court decisions MCP server require authentication?

No. We connected to lahend.ee — Estonian court decisions without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the lahend.ee — Estonian court decisions MCP server still maintained?

lahend.ee — Estonian court decisions is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.