Judikatura MCP — Slovak Court Decisions

io.github.adakov589Published by GitHub account adakov589v1.1.0Updated Oct 24, 2026

Slovak court decisions as MCP tools. 12,000+ decisions, GDPR-compliant, pseudonymized, SLA-backed.

VerifiedStreamable HTTPWeb executableKnowledge & Memory

Overview

AI-generated overview

A remote MCP server that gives an assistant access to a collection of Slovak court decisions, pseudonymized and GDPR-compliant.

What you can do
Search and retrieve Slovak court decisions through the hosted service, which reports over 12,000 decisions. Results are pseudonymized and described as GDPR-compliant, with an SLA-backed service. The manifest lists no individual tools, so the exact operations are not documented here.
When to use it
Useful when you need to look up or reference Slovak case law while working with an assistant, for example for legal research or drafting that depends on court decisions.
Requirements
A remote endpoint at api.lexvector.eu reached over streamable HTTP. OAuth authentication is required, so you need an account or credentials accepted by that service. No environment variables or headers are declared.
Before you install
You must authenticate through OAuth, which shares your identity with the third-party service. Queries and any retrieved case text are sent to that external provider. Decisions are described as pseudonymized, so verify suitability before relying on them for legal work.

Installation

In SourceWeft

  1. Open Judikatura MCP — Slovak Court Decisions in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. 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.adakov589%2Fjudikatura-mcp/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. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "judikatura-slovak-court-decisions": {
      "type": "http",
      "url": "https://api.lexvector.eu/mcp"
    }
  }
}

README

This repository has no README.

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.1.0LatestSep 16, 2026

Score

35% 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

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

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

  • License10 pts

    Declare a license in the repository or the registry entry.