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.

Entscheidsuche — Schweizer Gerichtsentscheide

REMOTE · MCP.ENTSCHEIDSUCHE.CH · SCANNED SEP 22

Suche in Schweizer Gerichtsentscheiden aller Instanzen (Bund, Kantone) in DE/FR/IT.

0 this week 80 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 Security60
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 5 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

Install

How do I install the Entscheidsuche — Schweizer Gerichtsentscheide MCP server?

Entscheidsuche — Schweizer Gerichtsentscheide is a hosted endpoint at https://mcp.entscheidsuche.ch/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.entscheidsuche.ch

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

  • 21 Sept 26 0
    • Endpoint reachability: reachable → unreachable security
    • HSTS header: fail → unverified security
    • Stability: pass → unverified security
    • Tool safety: pass → unverified security
    • Transport: pass → fail security
    • Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
    • Schema quality: 100 → unverified functional
    • Capabilities: pass → unverified functional
    • Tool coverage: 100 → unverified functional
  • 20 Sept 26 +16
    • HSTS header: unverified → fail security
    • Injection markers: unverified → pass security
    • Stability: unverified → pass security
    • Transport: fail → pass security
    • Authorization: Authorisation 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. security
    • Endpoint reachability: unreachable → reachable functional
    • Tool coverage: unverified → 100 functional
    • Schema quality: unverified → 100 functional
    • MCP protocol: unverified → pass functional
  • 19 Sept 26 −16

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 17 Sept 26 0
    • Endpoint reachability: reachable → unreachable security
    • HSTS header: fail → unverified security
    • Stability: pass → unverified security
    • Tool safety: pass → unverified security
    • Transport: pass → fail security
    • Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
    • Schema quality: 100 → unverified functional
    • Capabilities: pass → unverified functional
    • Tool coverage: 100 → unverified functional
  • 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
  • 17 Aug 26 0
    • Tool “fetch_document” rewrote its description, which is the text the model reads security
    • Tool “list_facets” rewrote its description, which is the text the model reads security
    • Tool “list_hierarchy” rewrote its description, which is the text the model reads security
    • Tool “search” rewrote its description, which is the text the model reads security
    • Tool “search_by_case_number” rewrote its description, which is the text the model reads security
    • Tool “server_info” rewrote its description, which is the text the model reads security
    • Schema quality: 205 → 184 functional
    • “fetch_document” reworded the description of “id” cosmetic
    • “fetch_document” reworded the description of “language” cosmetic
    • “list_hierarchy” reworded the description of “query” cosmetic
    • “list_hierarchy” reworded the description of “size” cosmetic
    • “search” reworded the description of “decision_date_from” cosmetic
    • “search” reworded the description of “decision_date_to” cosmetic
    • “search” reworded the description of “hierarchy” cosmetic
    • “search” reworded the description of “include_aggregations” cosmetic
    • “search” reworded the description of “language” cosmetic
    • “search” reworded the description of “language_filter” cosmetic
    • “search” reworded the description of “query” cosmetic
    • “search” reworded the description of “scrape_date_from” cosmetic
    • “search” reworded the description of “scrape_date_to” cosmetic
    • “search” reworded the description of “search_after” cosmetic
    • “search” reworded the description of “size” cosmetic
    • “search” reworded the description of “sort” cosmetic
    • “search_by_case_number” reworded the description of “case_number” cosmetic
    • “search_by_case_number” reworded the description of “decision_date_from” cosmetic
    • “search_by_case_number” reworded the description of “decision_date_to” cosmetic
    • “search_by_case_number” reworded the description of “hierarchy” cosmetic
    • “search_by_case_number” reworded the description of “include_aggregations” cosmetic
    • “search_by_case_number” reworded the description of “language” cosmetic
    • “search_by_case_number” reworded the description of “language_filter” cosmetic
    • “search_by_case_number” reworded the description of “scrape_date_from” cosmetic
    • “search_by_case_number” reworded the description of “scrape_date_to” cosmetic
    • “search_by_case_number” reworded the description of “search_after” cosmetic
    • “search_by_case_number” reworded the description of “size” cosmetic
    • “search_by_case_number” reworded the description of “sort” cosmetic
    • Tool “fetch_document” changed its title: Entscheid abrufen → Fetch decision cosmetic
    • Tool “list_facets” changed its title: Facetten-Baum (lokalisiert) → Facet tree (localized) cosmetic
    • Tool “list_hierarchy” changed its title: Hierarchie-Buckets → List hierarchy buckets cosmetic
    • Tool “search” changed its title: Entscheide durchsuchen → Search decisions cosmetic
    • Tool “search_by_case_number” changed its title: Nach Geschäftsnummer suchen → Search by case number cosmetic
    • Tool “server_info” changed its title: Server-Info → Server info cosmetic
  • 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
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 22 Sept 2026 · Probed https://mcp.entscheidsuche.ch/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.entscheidsuche.ch CN=YE2,O=Let's Encrypt,C=US 24 Aug 2026 22 Nov 2026 ECDSA 256 ECDSA-SHA384 69a2da0204706195d451639cfad146b5e02
SANs: mcp.entscheidsuche.ch
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 secure

Validation of mcp.entscheidsuche.ch. Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
ch. present 58745 13 Verified
entscheidsuche.ch. present 4260, 4260 13, 13 Verified
mcp.entscheidsuche.ch. Verified address RRset verified with the apex keys
Authentication Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.entscheidsuche.ch/mcp Unreachable
http (plaintext) http://mcp.entscheidsuche.ch/mcp HTTPS enforced 301 https://mcp.entscheidsuche.ch/mcp
MCP tools · 6 exposed · ~1,157 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
fetch_document ~156

Fetch a single Swiss court decision, judgment or Federal Supreme Court decision by its document ID (`_id`). Returns the indexed full text of the decision together with metadata, title, abstract and links. Use this when the full decision should be read or processed after a search. Note: for very long decisions the indexed text is capped at 100,000 characters; if `text_truncated` is true, the complete document is available at `document_url`.

NameTypeReqDescription
idstringyesDocument ID (e.g. 'CH_BGer_001_5A_123_2024_2024-06-15').
languageOptional preferred language for title/abstract. If omitted, the first available language field is returned.
NameTypeReqDescription
resultyes

No examples provided.

list_facets ~43

Hierarchical facet tree with localized labels for cantons, courts and chambers. The `id` fields can be used in the `hierarchy` filter of the search.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultarrayyes

No examples provided.

list_hierarchy ~70

Returns the available hierarchy IDs for Swiss cantons, courts and chambers together with document counts. Useful for narrowing subsequent searches to the Federal Supreme Court, cantonal courts, Obergerichte or Verwaltungsgerichte.

NameTypeReqDescription
querystringOptional full-text query.
sizeintegerMaximum number of entries.
NameTypeReqDescription
entriesarrayyes

No examples provided.

search ~515

Full-text search across Swiss court judgments, court decisions and case law from entscheidsuche.ch. Covers decisions of the Federal Supreme Court (BGer, BGE) and cantonal courts such as Kantonsgericht, Obergericht or Verwaltungsgericht. Typical use cases: - Search Federal Supreme Court judgments, BGE or rulings by topic - Find Swiss case law on tenancy law, ZGB, OR, StGB or BV - Verify case numbers, judgment numbers or citations - Related tools: fetch_document, search_by_case_number, list_hierarchy, list_facets Search syntax (Lucene query string): - Phrase / case-number search: "BGE 142 III 1" (in quotes) - Boolean operators: AND, OR, NOT (or +, -) - Wildcards: * and ? - The default operator between terms is AND. Filters are combined with AND. Use hierarchy IDs from `list_hierarchy` or `list_facets`. Pagination: after the first call, pass the `next_cursor` value from the response as `search_after` in the next call.

NameTypeReqDescription
decision_date_fromLower bound for the decision date (YYYY-MM-DD, inclusive).
decision_date_toUpper bound for the decision date (YYYY-MM-DD, inclusive).
hierarchyList of hierarchy IDs (canton/court/chamber). Multiple IDs are combined with OR; with other filters, AND.
include_aggregationsbooleanInclude aggregations (distributions over the results).
languageOptional preferred language for highlighting/display (de, fr, it). If omitted, the first available language field is returned — this does NOT filter; use `language_filter` for that.
language_filterFilter by document language(s).
querystringFull-text query. "..." for phrases, AND/OR/NOT for Boolean operators, * and ? for wildcards. "*" matches everything.
scrape_date_fromLower bound for the scrape date (YYYY-MM-DD, inclusive).
scrape_date_toUpper bound for the scrape date (YYYY-MM-DD, inclusive).
search_afterCursor from `next_cursor` of the previous response.
sizeintegerResults per page (1–100).
sortstringOptional sort order: 'relevance' | 'date' (decision date) | 'scrapedate'. Default is 'relevance'.
NameTypeReqDescription
aggregations
hitsarrayyes
next_cursorCursor for the next page. Pass it again as `search_after` in the next request. None if there are no further results.
totalintegeryes

No examples provided.

search_by_case_number ~347

Specialized search for case numbers, judgment numbers and BGE citations in Swiss court judgments. This tool automatically wraps the given case number in quotes and runs an exact phrase search, for example for 'BGE 142 III 1', '5A_396/2015' or similar references from the Federal Supreme Court (BGer, BGE) and cantonal case law.

NameTypeReqDescription
case_numberstringyesCase number (docket reference), BGE citation or judgment number, e.g. 'BGE 142 III 1' or '5A_396/2015'.
decision_date_fromOptional lower bound for the decision date (YYYY-MM-DD).
decision_date_toOptional upper bound for the decision date (YYYY-MM-DD).
hierarchyOptional hierarchy IDs for canton/court/chamber.
include_aggregationsbooleanOptionally include aggregations.
languageOptional preferred language for highlighting/display (de, fr, it). If omitted, the first available language field is returned — this does NOT filter; use `language_filter` for that.
language_filterOptional filter by document language(s).
scrape_date_fromOptional lower bound for the scrape date (YYYY-MM-DD).
scrape_date_toOptional upper bound for the scrape date (YYYY-MM-DD).
search_afterCursor from `next_cursor` of the previous response.
sizeintegerResults per page (1–100).
sortstringOptional sort order: 'relevance' | 'date' (decision date) | 'scrapedate'. Default is 'relevance'.
NameTypeReqDescription
aggregations
hitsarrayyes
next_cursorCursor for the next page. Pass it again as `search_after` in the next request. None if there are no further results.
totalintegeryes

No examples provided.

server_info ~26

Version info and configured endpoint URLs of the MCP server for Swiss case law and court decisions.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

Common questions

What is the Entscheidsuche — Schweizer Gerichtsentscheide MCP server?

Entscheidsuche — Schweizer Gerichtsentscheide is an MCP server listed in the public MCP registry as ch.entscheidsuche/mcp. Suche in Schweizer Gerichtsentscheiden aller Instanzen (Bund, Kantone) in DE/FR/IT. This page covers its hosted endpoint (https://mcp.entscheidsuche.ch/mcp).

Is the Entscheidsuche — Schweizer Gerichtsentscheide MCP server safe to use?

Entscheidsuche — Schweizer Gerichtsentscheide scores 80 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 Entscheidsuche — Schweizer Gerichtsentscheide MCP server expose?

Entscheidsuche — Schweizer Gerichtsentscheide exposes 6 tools: search, search_by_case_number, fetch_document, list_hierarchy, list_facets, server_info. Their descriptions and schemas cost roughly 1,157 tokens of context every time the server is loaded.

Does the Entscheidsuche — Schweizer Gerichtsentscheide MCP server require authentication?

Its publisher declares no required credentials for Entscheidsuche — Schweizer Gerichtsentscheide. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

Is the Entscheidsuche — Schweizer Gerichtsentscheide MCP server still maintained?

Entscheidsuche — Schweizer Gerichtsentscheide is still listed in the MCP registry, though our most recent checks did not reach this channel. 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.