Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
Open Legal Data (Germany) is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
93/100
tool-list score
19
tools declared
remote
at its publisher
—
calls last 7d
What it does
German court decisions (Rechtsprechung) and laws (Gesetze) with citation graph and citation checks.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http open-legal-data-germany-mcp https://de.openlegaldata.io/mcp
# 2 — ask your agent for something these tools do
# get_server_instructions, get_court, list_courts and 16 more
Open Legal Data (Germany) costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
OPAll 1 server
openlegaldata1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http open-legal-data-germany-mcp https://de.openlegaldata.io/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
19 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Return MCP server instructions (if any). Always call first.
No parameter schema on file.
Get detailed information about a specific court. Look up a court by ID, slug, or code. Returns full details including address, contact information, and case count. Args: court_id: Court database ID. slug: Court slug (e.g. "ag-charlottenburg"). code: Court ECLI code (e.g. "AGBECH" for the Amtsgericht Charlottenburg, "BGH"
| Parameter | Type | Required | Notes |
|---|---|---|---|
| court_id | integer | no | — |
| slug | string | no | — |
| code | string | no | — |
Browse and filter German courts. Returns a list of courts matching the given filters. Use this to discover which courts are available before searching for cases. Args: court_type: Filter by court type code (e.g. "AG", "LG", "OLG", "BGH", "VG", "OVG", "BVerwG", "ArbG", "LAG", "BAG"). state: Filter by state name or slug (e.g. "Berlin"
| Parameter | Type | Required | Notes |
|---|---|---|---|
| court_type | string | no | — |
| state | string | no | — |
| jurisdiction | string | no | — |
| level_of_appeal | string | no | — |
| search | string | no | — |
| limit | integer | no | — |
Structured filtering of court cases using the database. Unlike search_cases (which uses full-text search), this tool filters cases using exact database fields. Returns case metadata without full content, newest first, with `total and has_more. If an exact count takes too long, total is a lower bound and total_is_lower_bound` is true. A filter
| Parameter | Type | Required | Notes |
|---|---|---|---|
| court_id | integer | no | — |
| court_slug | string | no | — |
| date_after | string | no | — |
| date_before | string | no | — |
| file_number | string | no | — |
| ecli | string | no | — |
| decision_type | string | no | — |
| limit | integer | no | — |
| offset | integer | no | — |
Retrieve a court case by ID or slug. By default returns the case metadata and the complete, untruncated `content as plain text (HTML tags removed, entities decoded, whitespace normalized; one line per paragraph, Randnummern as line prefix). To read a long decision piece by piece, request a snippet with offset and/or length`; both count characters
| Parameter | Type | Required | Notes |
|---|---|---|---|
| case_id | integer | no | — |
| slug | string | no | — |
| offset | integer | no | — |
| length | integer | no | — |
| full_text | no | — |
Get aggregated case statistics. Returns case counts grouped by time period, optionally filtered by court, state, or jurisdiction. Without `date_after only the last 12 months are counted. For counts over a longer period ("per year since 2018"), pass date_after (e.g. "2018-01-01") together with group_by="year". The response's `date_ra
| Parameter | Type | Required | Notes |
|---|---|---|---|
| court_id | integer | no | — |
| state | string | no | — |
| jurisdiction | string | no | — |
| date_after | string | no | — |
| date_before | string | no | — |
| group_by | string | no | — |
Find court cases textually similar to a given case. Seeds an Elasticsearch "more like this" query with the full text of the given case and returns the most similar OTHER cases, ranked by similarity. Useful for comparative research: once you have one on-point decision, surface neighbouring case law without crafting a keyword query. For keyword- or citation-s
| Parameter | Type | Required | Notes |
|---|---|---|---|
| case_id | integer | yes | — |
| limit | integer | no | — |
Full-text search for German court cases via Elasticsearch. Returns matching cases (with `file_number) and highlighted snippets. Does NOT return full case text - use get_case to retrieve complete content. The citation filters compose with query so you can answer "cases citing § 823 BGB that mention 'Mietrecht'" in one call — pass `query="Mie
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | — |
| court_code | string | no | — |
| start_date | string | no | — |
| end_date | string | no | — |
| decision_type | string | no | — |
| cited_law_book | string | no | — |
| cited_law_section | string | no | — |
| cited_case_id | integer | no | — |
| sort | string | no | — |
| limit | integer | no | — |
Get the full text of a specific law section. Retrieve law text by book code and section number, or by law ID. For example, get_law_section(book_code="BGB", section="823") returns the text of section 823 of the German Civil Code. By default the complete, untruncated `content` is returned as plain text (HTML tags removed, entities decoded, whitespace norma
| Parameter | Type | Required | Notes |
|---|---|---|---|
| book_code | string | no | — |
| section | string | no | — |
| law_id | integer | no | — |
| offset | integer | no | — |
| length | integer | no | — |
List available German law books (e.g. BGB, StGB, GG). Returns law books with their codes, titles, and section counts. Use this to discover what legislation is available before searching for specific law sections. Args: latest_only: Only show latest revisions (default True). search: Search book codes and titles. Best matches come first
| Parameter | Type | Required | Notes |
|---|---|---|---|
| latest_only | boolean | no | — |
| search | string | no | — |
| limit | integer | no | — |
Full-text search across law sections via Elasticsearch. Returns matching law sections with highlighted snippets. Does NOT return full text - use get_law_section to retrieve the complete content of a specific section. Args: query: Search query text (supports Lucene syntax). book_code: Optional filter by law book code, any case (e.g.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | — |
| book_code | string | no | — |
| limit | integer | no | — |
Get forward references FROM a case (what this case cites). Returns all laws and cases that the given case references in its text. Useful for understanding the legal basis of a decision. Args: case_id: The database ID of the case.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| case_id | integer | yes | — |
Find all cases that cite a specific law section. Returns cases that reference the given statute section in their text. Useful for understanding how courts interpret a specific provision. To narrow the citing set by keyword, court, or date, use `search_cases(query=..., cited_law_book=..., cited_law_section=...)` instead. Args: book_cod
| Parameter | Type | Required | Notes |
|---|---|---|---|
| book_code | string | no | — |
| section | string | no | — |
| law_id | integer | no | — |
| sort | string | no | — |
| limit | integer | no | — |
Get reverse references TO a case (cases that cite this case). Find all cases that reference the given case in their text. Useful for understanding the impact and precedent value of a decision. To narrow the citing set by keyword, court, or date, use `search_cases(query=..., cited_case_id=case_id)` instead. Args: case_id: The database ID of th
| Parameter | Type | Required | Notes |
|---|---|---|---|
| case_id | integer | yes | — |
| sort | string | no | — |
| limit | integer | no | — |
Check if a legal citation exists in the OLDP database. Validates Aktenzeichen (file numbers), ECLI identifiers, or paragraph references (e.g. "§ 823 BGB"). Use this to verify citations before presenting them to users. Args: citation: The citation to validate (e.g. "VI ZR 123/22", "ECLI:DE:BGH:2023:...", "§ 823 BGB"). citatio
| Parameter | Type | Required | Notes |
|---|---|---|---|
| citation | string | yes | — |
| citation_type | string | no | — |
Send feedback about OLDP or this MCP server to the OLDP team. Use this to report bugs (wrong results, errors, broken tools), problems with the legal data (missing or wrong decisions, laws or references), or to request features. Only submit feedback the user wants to send or has agreed to; do not include personal data or confidential case details. Requires a
| Parameter | Type | Required | Notes |
|---|---|---|---|
| category | string | yes | — |
| message | string | yes | — |
| subject | string | no | — |
| context | string | no | — |
Get OLDP platform coverage summary. Returns an overview of the data available on the Open Legal Data Platform, including counts of cases, laws, courts, and references. Call this first to understand what data you can search and retrieve.
No parameter schema on file.
Search BOTH legislation and court cases in one call. Returns the most relevant law sections AND court decisions for the query, grouped by type. Use this when a legal question may be answered by statute or by case law and you don't yet know which — e.g. "ortsübliche Vergleichsmiete" surfaces § 558 BGB *and* BGH decisions together. For type-specific contr
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | — |
| limit | integer | no | — |
Show who you are connected as and your remaining request budget. Call this before a long task to check how many requests are left, or to learn how to get a larger budget. Every HTTP request to the MCP server counts against the budget, including this call; once nothing is left, requests (this one too) are rejected with HTTP 429 until the window frees up. Ret
No parameter schema on file.
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Open Legal Data (Germany) or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 93 / 100
Release 0.16.5 · scanned 11 Nov 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score93
Findings0 threat · 1 capability
Capabilitymoderate
Coveragemanifest
Verificationnot in this report
Surface digest688bec5f16c6cb168068cd01bfc668a5a826c261d3593d03ba440c73939b3047
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| get_server_instructions | no tags | |
| get_court | no tags | |
| list_courts | untrusted-input | untrusted-input: keyword "browse" |
| filter_cases | no tags | |
| get_case | no tags | |
| get_case_statistics | no tags | |
| get_similar_cases | no tags | |
| search_cases | no tags | |
| get_law_section | no tags | |
| list_law_books | no tags | |
| search_laws | no tags | |
| get_case_references | no tags | |
| get_cases_for_law | no tags | |
| get_citing_cases | no tags | |
| validate_citation | no tags | |
| submit_feedback | state-write | state-write: declares readOnlyHint: false |
| get_platform_info | no tags | |
| search_legal | no tags | |
| whoami | external-sink | external-sink: keyword "http_request" |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
flow-1
Untrusted input can drive an external action even though no sensitive source is exposed.
Supply chain and provenance
Integrityfirst-seen
Surface digest688bec5f16c6cb16
Scanned2026-11-11
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.16.5.
0.16.5
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Open Legal Data (Germany) can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.