Swiss Case Law MCP Server

https://mcp.opencaselaw.ch/ Remote v1.27.0

Published by mcp.opencaselaw.ch — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.

956k Swiss court decisions: full-text search, citation graph, statute lookup (DE/FR/IT)

Trust grade
A
97/100
Last scanned get badge →
Trust
A · 97/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Moderate
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Live
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 97/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 3 = 97. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−3 capability blast radius (moderate) — client exposure if the model is manipulated

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 41

Each tool and what it can reach — enumerated from the running server.

  • browse_legislation_changesingests untrusted input
  • fetchingests untrusted input
  • get_decisioningests untrusted input
  • get_scholarshipingests untrusted input
  • get_scholarship_full_textingests untrusted input
  • search_legislationingests untrusted input
  • analyze_legal_trendno sensitive capability
  • attest_responseno sensitive capability
  • check_claim_supportno sensitive capability
  • citeno sensitive capability
Show 31 more tools ↓
  • draft_mock_decisionno sensitive capability
  • find_appeal_chainno sensitive capability
  • find_citationsno sensitive capability
  • find_leading_casesno sensitive capability
  • find_relevant_erwaegungno sensitive capability
  • find_scholarship_citing_decisionno sensitive capability
  • find_scholarship_citing_statuteno sensitive capability
  • generate_exam_questionno sensitive capability
  • get_article_historyno sensitive capability
  • get_article_purposeno sensitive capability
  • get_case_briefno sensitive capability
  • get_commentaryno sensitive capability
  • get_decision_structureno sensitive capability
  • get_doctrineno sensitive capability
  • get_erwaegungno sensitive capability
  • get_lawno sensitive capability
  • get_legislationno sensitive capability
  • get_materialienno sensitive capability
  • get_practiceno sensitive capability
  • get_regesteno sensitive capability
  • get_statisticsno sensitive capability
  • list_courtsno sensitive capability
  • list_scholarship_sourcesno sensitive capability
  • searchno sensitive capability
  • search_botschaftno sensitive capability
  • search_commentariesno sensitive capability
  • search_decisionsno sensitive capability
  • search_lawsno sensitive capability
  • search_materialienno sensitive capability
  • search_practiceno sensitive capability
  • search_scholarshipno sensitive capability

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v1.27.0 latest A 97/100 0 1.10.0 2026-07-25

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 97/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/mcp-opencaselaw-ch/badge.svg)](https://mcptrustchecker.com/registry/mcp-opencaselaw-ch)
HTML
<a href="https://mcptrustchecker.com/registry/mcp-opencaselaw-ch"><img src="https://mcptrustchecker.com/registry/mcp-opencaselaw-ch/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/mcp-opencaselaw-ch/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan https://mcp.opencaselaw.ch/ --online

Use the free API → How scoring works

More in Web, Search & Scraping