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.

io.github.malkreide/swiss-courts-mcp

PYPI · SWISS-COURTS-MCP · SCANNED SEP 20

Swiss court decisions via entscheidsuche.ch, including federal and cantonal courts

Available components

−15 this week 65 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security50
  • Malware scan not yet available for this package.Unverified
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
  • 1 of 34 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency35
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • License check failed: the license (MIT License) isn't a recognized OSI-approved license. See how to fix → Fail
  • Actively maintained (last published 0 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability80
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 713 tokens (~89/item across 8 items; 8 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
  • Stability observed for 28 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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 9 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
Install

How do I install the io.github.malkreide/swiss-courts-mcp server?

io.github.malkreide/swiss-courts-mcp runs locally as a PyPI package, launched with uvx swiss-courts-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · swiss-courts-mcp

# add to Claude Code
claude mcp add malkreide-swiss-courts-mcp -- uvx swiss-courts-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "malkreide-swiss-courts-mcp": {
      "command": "uvx",
      "args": [
        "swiss-courts-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "malkreide-swiss-courts-mcp": {
      "command": "uvx",
      "args": [
        "swiss-courts-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add malkreide-swiss-courts-mcp -- uvx swiss-courts-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "malkreide-swiss-courts-mcp": {
      "type": "local",
      "command": [
        "uvx",
        "swiss-courts-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add malkreide-swiss-courts-mcp --command uvx --arg swiss-courts-mcp
# ~/.hermes/config.yaml
mcp_servers:
  malkreide-swiss-courts-mcp:
    command: "uvx"
    args: ["swiss-courts-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "malkreide-swiss-courts-mcp": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "swiss-courts-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add malkreide-swiss-courts-mcp -t stdio -c uvx -a swiss-courts-mcp
// mcp.json
{
  "mcpServers": {
    "malkreide-swiss-courts-mcp": {
      "command": "uvx",
      "args": [
        "swiss-courts-mcp"
      ]
    }
  }
}
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.

  • 20 Sept 26 −14
    • Malware scan: pass → unverified security
  • 19 Sept 26 +15
    • Stability: 0.87 → unverified security
    • Tool safety: pass → unverified security
    • Malware scan: unverified → pass security
    • Capabilities: pass → unverified functional
    • Tool coverage: 100 → unverified functional
    • Schema quality: 100 → unverified functional
    • Package version: 0.4.0 → 0.5.0 functional
  • 18 Sept 26 +1

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

  • 17 Sept 26 −15
    • Malware scan: pass → unverified security
  • 16 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 15 Sept 26 +16
    • Malware scan: unverified → pass security
    • Stability: 0.97 → pass security
  • 14 Sept 26 −15
    • Malware scan: pass → unverified security
  • 13 Sept 26 −1
    • Stability: pass → 0.93 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 20 Sept 2026 · Analysed pypi/swiss-courts-mcp@0.5.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem pypi

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted hatchling.build

Background: Why install scripts are a supply-chain risk →

Dependencies 34 packages
Packages resolved 34
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 8 exposed · ~618 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
get_court_decision ~63

Ruft einen einzelnen Gerichtsentscheid anhand seiner Signatur ab. Use-Case: Detail-Ansicht eines konkreten Urteils (Signatur aus search_court_decisions). Exakter Lookup ohne Fuzzy-Fallback.

NameTypeReqDescription
paramsyes

No output schema declared.

No examples provided.

get_decision_statistics ~47

Gibt Statistiken über die Anzahl indexierter Gerichtsentscheide zurück. Use-Case: Mengengerüst und Verteilung nach Kanton/Jahr.

NameTypeReqDescription
paramsyes

No output schema declared.

No examples provided.

get_fallback_status ~122

Zeigt Zustand und Abdeckung des Offline-Fallbacks (SCD-Dump). Use-Case: Transparenz — ist der lokale Dump-Cache vorhanden, welche Version, was deckt er ab (nur Bundesgericht 2007–2024, kein Volltext) und wie erzwingt man ihn (ENV ``SWISS_COURTS_FORCE_DUMP=1``). Read-only; lädt selbst NICHTS herunter. ``check_updates=True`` fragt optional die Zenodo-Versions-API ab.

NameTypeReqDescription
paramsyes

No output schema declared.

No examples provided.

get_recent_decisions ~53

Gibt die neuesten Gerichtsentscheide zurück. Use-Case: aktuelle Rechtsprechungsentwicklungen verfolgen. Chronologisch sortiert, filterbar nach Kanton und Gerichtsebene.

NameTypeReqDescription
paramsyes

No output schema declared.

No examples provided.

list_courts ~54

Listet alle in entscheidsuche.ch indexierten Gerichte auf. Use-Case: Überblick über verfügbare Bundes- und Kantonsgerichte, optional nach Kanton gefiltert.

NameTypeReqDescription
paramsyes

No output schema declared.

No examples provided.

search_bger_decisions ~51

Sucht gezielt in Bundesgerichtsentscheiden (BGer/BGE). Use-Case: höchstrichterliche Rechtsprechung mit optionalem Abteilungsfilter.

NameTypeReqDescription
paramsyes

No output schema declared.

No examples provided.

search_by_law_reference ~115

Sucht Gerichtsentscheide die einen bestimmten Gesetzesartikel zitieren. Use-Case: Praxis zu einer Norm finden. Mehrstufige Suche: exakte Phrase (höchste Relevanz) + Artikelnummer/Kürzel (breitere Abdeckung). Synergie mit fedlex-mcp: zuerst Gesetz nachschlagen, dann Praxis dazu finden. Beispiele: 'Art. 8 BV', 'Art. 328 OR', 'Art. 25 DSG'.

NameTypeReqDescription
paramsyes

No output schema declared.

No examples provided.

search_court_decisions ~113

Volltextsuche in Schweizer Gerichtsentscheiden. Use-Case: juristische Recherche über alle Schweizer Gerichte (Bund + Kantone) via entscheidsuche.ch. Unterstützt Filter nach Kanton, Gerichtsebene und Datumsbereich. Liefert abgeschlossene Treffer inkl. Titel, Abstract und Volltext-Link, kuratiertes Markdown sowie einen maschinenlesbaren Response-Envelope (source, license, match_type, count, total, results).

NameTypeReqDescription
paramsyes

No output schema declared.

No examples provided.

Common questions

What is the io.github.malkreide/swiss-courts-mcp server?

io.github.malkreide/swiss-courts-mcp is listed in the public MCP registry as io.github.malkreide/swiss-courts-mcp. Swiss court decisions via entscheidsuche.ch, including federal and cantonal courts. This page covers its PyPI package (swiss-courts-mcp).

Is the io.github.malkreide/swiss-courts-mcp server safe to use?

io.github.malkreide/swiss-courts-mcp scores 65 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. 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 io.github.malkreide/swiss-courts-mcp server expose?

io.github.malkreide/swiss-courts-mcp exposes 8 tools: search_court_decisions, get_court_decision, search_bger_decisions, search_by_law_reference, list_courts, and 3 more. Their descriptions and schemas cost roughly 618 tokens of context every time the server is loaded.

Is the io.github.malkreide/swiss-courts-mcp server still maintained?

io.github.malkreide/swiss-courts-mcp 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.