Open Legal Data (Germany)
REMOTE · DE.OPENLEGALDATA.IO
German court decisions (Rechtsprechung) and laws (Gesetze) with citation graph and citation checks.
Available components
Last scanned (19 hours ago)
Scores higher than 56% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Education and Research
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 Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability63
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 5104 tokens (~268/item across 19 items; 19 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
- Stability observed for 11 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
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 20 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 19 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Nov 26 +1
- Tool “filter_cases” rewrote its description, which is the text the model reads security
- Tool “get_case_statistics” rewrote its description, which is the text the model reads security
- Tool “get_court” rewrote its description, which is the text the model reads security
- Tool “list_law_books” rewrote its description, which is the text the model reads security
- Tool “search_cases” rewrote its description, which is the text the model reads security
- Tool “search_laws” rewrote its description, which is the text the model reads security
- Tool “search_legal” rewrote its description, which is the text the model reads security
- Tool “submit_feedback” rewrote its description, which is the text the model reads security
- Stability: unverified → 0.03 ▲ functional
- 10 Nov 26 66
First indexed and scored.
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 21 Nov 2026 · Probed https://de.openlegaldata.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=openlegaldata.io | CN=YE1,O=Let's Encrypt,C=US | 2 Nov 2026 | 31 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 524105fc9e1caebf2d4d51e7cbe755bc17c |
| SANs: *.openlegaldata.io, openlegaldata.io | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| 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 insecure
Validation of de.openlegaldata.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| io. | DS published | 38690 | 8 | Verified |
| openlegaldata.io. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | same-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://de.openlegaldata.io/mcp | Verified | 200 | |
| http (plaintext) | http://de.openlegaldata.io/mcp | HTTPS enforced | 301 | https://de.openlegaldata.io/mcp |
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 →
filter_cases Filter court decisions ~359
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 combination too broad to answer in time (e.g. a rare ``decision_type`` without court or date filter) returns an ``error`` with a ``hint`` to narrow it. Args: court_id: Filter by court database ID. court_slug: Filter by court slug (e.g. "bgh"). date_after: Cases from this date onward (YYYY-MM-DD). date_before: Cases up to this date (YYYY-MM-DD). file_number: Exact file number (Aktenzeichen). ecli: Exact ECLI identifier. decision_type: Decision type (e.g. "Urteil", "Beschluss"). limit: Maximum results (default 20, max 50). Values above 50 are clamped; the response then includes ``limit_clamped: true`` and the original ``requested_limit``. offset: Skip first N results for pagination (default 0).
| Name | Type | Req | Description |
|---|---|---|---|
| court_id | integer | – | – |
| court_slug | string | – | – |
| date_after | string | – | – |
| date_before | string | – | – |
| decision_type | string | – | – |
| ecli | string | – | – |
| file_number | string | – | – |
| limit | integer | – | – |
| offset | integer | – | – |
No output schema declared.
No examples provided.
get_case Get court decision ~302
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 of that plain text. In snippet mode ``content`` is omitted and a ``snippet`` object is returned: ``text``, ``offset``, ``length``, ``total_length``, ``has_more`` and ``next_offset``. Pass ``next_offset`` as ``offset`` to continue reading until ``has_more`` is false. Args: case_id: Case database ID. slug: Case URL slug. offset: Start position in plain-text characters (default 0). length: Number of plain-text characters to return. 0 (default) means "until the end". Leave both at 0 for the full content. full_text: Deprecated and ignored (content is never truncated). Passing it adds a ``deprecation_warnings`` entry to the response.
| Name | Type | Req | Description |
|---|---|---|---|
| case_id | integer | – | – |
| full_text | – | – | – |
| length | integer | – | – |
| offset | integer | – | – |
| slug | string | – | – |
No output schema declared.
No examples provided.
get_case_references Get references in a decision ~72
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.
| Name | Type | Req | Description |
|---|---|---|---|
| case_id | integer | yes | – |
No output schema declared.
No examples provided.
get_case_statistics Get court decision statistics ~346
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_range`` shows the period that was counted. Args: court_id: Filter by court ID. state: Filter by state name or slug. jurisdiction: Filter by jurisdiction. Accepts the English shortcuts ("ordinary", "labor", …) or the stored German values ("Ordentliche Gerichtsbarkeit", …). date_after: Count cases from this date (YYYY-MM-DD, default: 365 days ago). date_before: Count cases up to this date (YYYY-MM-DD, default: today). group_by: Time grouping: "month" (default) or "year". Returns an ``{"error": ...}`` payload (instead of silently zero results) when an unknown court_id, state, jurisdiction, group_by, or malformed date is supplied — the previous behavior swallowed bad inputs as ``total: 0`` and was the dangerous failure mode called out in the MCP audit.
| Name | Type | Req | Description |
|---|---|---|---|
| court_id | integer | – | – |
| date_after | string | – | – |
| date_before | string | – | – |
| group_by | string | – | – |
| jurisdiction | string | – | – |
| state | string | – | – |
No output schema declared.
No examples provided.
get_cases_for_law Find decisions citing a law ~257
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_code: Law book code (e.g. "BGB", "StGB"). section: Section identifier (e.g. "823"). law_id: Direct law database ID (alternative to book_code+section). sort: "date" (default, newest first) or "most_cited" — the latter surfaces the landmark decisions interpreting this provision (most-cited first). limit: Maximum results (default 20, max 50). Values above 50 are clamped; the response then includes ``limit_clamped: true`` and the original ``requested_limit``.
| Name | Type | Req | Description |
|---|---|---|---|
| book_code | string | – | – |
| law_id | integer | – | – |
| limit | integer | – | – |
| section | string | – | – |
| sort | string | – | – |
No output schema declared.
No examples provided.
get_citing_cases Find decisions citing a decision ~193
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 the cited case. sort: "date" (default, newest first) or "most_cited" (the most influential citing cases first). limit: Maximum results (default 20, max 50). Values above 50 are clamped; the response then includes ``limit_clamped: true`` and the original ``requested_limit``.
| Name | Type | Req | Description |
|---|---|---|---|
| case_id | integer | yes | – |
| limit | integer | – | – |
| sort | string | – | – |
No output schema declared.
No examples provided.
get_court Get court details ~125
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").
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | – | – |
| court_id | integer | – | – |
| slug | string | – | – |
No output schema declared.
No examples provided.
get_law_section Get law section ~463
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 normalized; one line per paragraph or list item). Set ``offset`` and/or ``length`` to get a ``snippet`` of that plain text instead (see get_case for the snippet fields and pagination via ``next_offset``). Args: book_code: Law book code (e.g. "BGB", "StGB", "GG"). section: Section identifier. Accepts bare numbers ("823", "20", "16a") or prefixed forms ("§ 823", "§823", "Art. 14", "Art 14", "Artikel 1"). The prefix spelling does not have to match the book: "Art. 20", "Artikel 20" and "20" all find Art 20 GG. Only exact sections match, never a longer number that contains the input. The ``section`` field on the response is whatever the DB stores, which differs by book convention: BGB / StGB / ZPO etc. store ``§ N`` (e.g. ``"§ 823"``), article-based books store e.g. ``"Art 1"`` (GG) or ``"Art. 6"`` (DSGVO). law_id: Direct law database ID (alternative to book_code+section). offset: Start position in plain-text characters (default 0). length: Number of plain-text characters to return. 0 (default) means "until the end". Leave both at 0 for the full content.
| Name | Type | Req | Description |
|---|---|---|---|
| book_code | string | – | – |
| law_id | integer | – | – |
| length | integer | – | – |
| offset | integer | – | – |
| section | string | – | – |
No output schema declared.
No examples provided.
get_platform_info Get platform coverage ~60
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_server_instructions Get server instructions ~22
Return MCP server instructions (if any). Always call first.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_similar_cases Find similar court decisions ~173
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-scoped neighbours instead, use search_cases. Args: case_id: The database ID of the seed case. limit: Maximum results (default 10, max 50). Values above 50 are clamped; the response then includes ``limit_clamped: true`` and the original ``requested_limit``.
| Name | Type | Req | Description |
|---|---|---|---|
| case_id | integer | yes | – |
| limit | integer | – | – |
No output schema declared.
No examples provided.
list_courts List courts ~372
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", "bayern"). jurisdiction: Filter by jurisdiction. Accepts the English shortcuts "ordinary", "administrative", "labor", "social", "fiscal", "constitutional" or the stored German values ("Arbeitsgerichtsbarkeit", …). The Bundespatentgericht (BPatG) belongs to ``ordinary``; there is no separate patent-jurisdiction category — filter on ``court_type="BPatG"`` if you specifically want patent cases. level_of_appeal: Filter by court level. Accepts the English shortcuts "local", "regional", "high", "federal" or the stored German values ("Amtsgericht", …). search: Search court names and aliases. limit: Maximum results to return (default 50, max 100). Values above 100 are clamped; the response then includes ``limit_clamped: true`` and the original ``requested_limit``.
| Name | Type | Req | Description |
|---|---|---|---|
| court_type | string | – | – |
| jurisdiction | string | – | – |
| level_of_appeal | string | – | – |
| limit | integer | – | – |
| search | string | – | – |
| state | string | – | – |
No output schema declared.
No examples provided.
list_law_books List law books ~231
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 (exact code, code prefix, code part, whole word in the title, part of a title word); ``match`` on each result says which. If ``search`` is exactly a book code, titles that only contain it inside a longer word (e.g. "BGBl." for "BGB") are left out. limit: Maximum results (default 50, max 200). Values above 200 are clamped; the response then includes ``limit_clamped: true`` and the original ``requested_limit``.
| Name | Type | Req | Description |
|---|---|---|---|
| latest_only | boolean | – | – |
| limit | integer | – | – |
| search | string | – | – |
No output schema declared.
No examples provided.
search_cases Search court decisions ~667
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="Mietrecht"`` together with ``cited_law_book="bgb"`` and ``cited_law_section="823"``. For "give me ALL citing cases" without keyword refinement, prefer the dedicated ``get_cases_for_law`` / ``get_citing_cases`` tools. ``cited_case_id`` is mutually exclusive with the law citation filter — if both are supplied, the law filter wins. Args: query: Search query text (supports Lucene syntax). court_code: Filter by court code (e.g. "BGH", "BVerfG"). start_date: Filter cases from this date (YYYY-MM-DD). end_date: Filter cases up to this date (YYYY-MM-DD). decision_type: Filter by decision type (e.g. "Urteil", "Beschluss"). cited_law_book: Restrict to cases citing a law from this book slug (e.g. "bgb"). Requires ``cited_law_section``. cited_law_section: Restrict to cases citing this law section slug, as in the ``slug`` of get_law_section (e.g. "823" for § 823 BGB, "art-14" for Art. 14 GG). Requires ``cited_law_book``. cited_case_id: Restrict to cases citing the case with this id. sort: Result order — "relevance" (default), "date" (newest first), or "most_cited" (most-cited first, for finding landmark precedent). The response echoes the applied ``sort``; any other value returns an error. Each result carries ``citing_cases_count`` so you can see how often it is cited. With relevance sort each…
| Name | Type | Req | Description |
|---|---|---|---|
| cited_case_id | integer | – | – |
| cited_law_book | string | – | – |
| cited_law_section | string | – | – |
| court_code | string | – | – |
| decision_type | string | – | – |
| end_date | string | – | – |
| limit | integer | – | – |
| query | string | yes | – |
| sort | string | – | – |
| start_date | string | – | – |
No output schema declared.
No examples provided.
search_laws Search laws ~183
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. "BGB", "BranntwMonG"). An unknown code returns an error with ``suggestions`` instead of an empty result. limit: Maximum results (default 10, max 50). Values above 50 are clamped; the response then includes ``limit_clamped: true`` and the original ``requested_limit``.
| Name | Type | Req | Description |
|---|---|---|---|
| book_code | string | – | – |
| limit | integer | – | – |
| query | string | yes | – |
No output schema declared.
No examples provided.
search_legal Search laws and court decisions ~342
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 control (citation filters, court/date filters), use ``search_cases`` / ``search_laws``. Matching is on the words of the text: a law section is found only if it contains the query terms. Colloquial terms that the statute doesn't use (e.g. "Eigenbedarf"; § 573 BGB says "die Räume als Wohnung für sich ... benötigt") find case law but not that section. Then search with the statute's wording, or read the cases' cited sections via ``get_case_references``. Results are grouped rather than merged into one ranked list on purpose: court decisions are long and out-score short statute texts on relevance, so a naive merged ranking returns only cases and buries the on-point law. Args: query: Search query text (supports Lucene syntax and "phrases"). limit: Max results per type (default 5, max 25). Values above 25 are clamped; the response then includes ``limit_clamped: true`` and the original ``requested_limit``.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | – |
No output schema declared.
No examples provided.
submit_feedback Send feedback to OLDP ~294
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 signed-in connection (OAuth or API token); anonymous calls are answered with HTTP 401 and an OAuth challenge, so the client can offer the user to sign in. Args: category: One of ``feature_request``, ``bug_report``, ``data_issue`` or ``other``. message: The feedback itself, in English or German (20-5000 characters). For bugs, describe what you did, what you expected and what happened instead. subject: Optional one-line summary (max 200 characters). context: Optional technical context (max 2000 characters), e.g. the tool name and arguments involved, case IDs, ECLI or law references. Returns: ``{"submitted": true, ...}`` on success, otherwise ``{"error": ...}``.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | yes | – |
| context | string | – | – |
| message | string | yes | – |
| subject | string | – | – |
No output schema declared.
No examples provided.
validate_citation Validate legal citation ~151
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"). citation_type: Type hint: "auto" (default), "file_number", "ecli", or "law_reference".
| Name | Type | Req | Description |
|---|---|---|---|
| citation | string | yes | – |
| citation_type | string | – | – |
No output schema declared.
No examples provided.
whoami Show connection and rate limit ~316
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. Returns: - ``authenticated``: whether the connection is signed in. - ``user``: ``username`` and ``profile_complete``, or null. - ``auth_method``: ``oauth``, ``api_token``, ``legacy_token`` or ``session``; null when anonymous. - ``rate_limit``: ``tier`` (``anonymous``, ``registered``, ``enriched`` or ``custom``), ``bucket`` (``shared`` when all anonymous users of this connector share one budget, ``ip`` or ``user``), ``limit`` per ``window_seconds``, ``used``, ``remaining``, and ``retry_after_seconds`` once nothing is left. Signed-in users share one budget between MCP and the REST API. - ``upgrade``: how to get a larger budget (``action``, ``url``, ``limit``, ``message``), or null. Pass the ``message`` and ``url`` on to the user when the budget is too small for the task.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the Open Legal Data (Germany) MCP server?
Open Legal Data (Germany) is a hosted endpoint at https://de.openlegaldata.io/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 · de.openlegaldata.io
claude mcp add --transport http io-openlegaldata-de 'https://de.openlegaldata.io/mcp'
What is the Open Legal Data (Germany) MCP server?
Open Legal Data (Germany) is an MCP server listed in the public MCP registry as io.openlegaldata/de. German court decisions (Rechtsprechung) and laws (Gesetze) with citation graph and citation checks. This page covers its hosted endpoint (https://de.openlegaldata.io/mcp).
Is the Open Legal Data (Germany) MCP server safe to use?
Open Legal Data (Germany) scores 71 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 Open Legal Data (Germany) MCP server expose?
Open Legal Data (Germany) exposes 19 tools: get_server_instructions, get_court, list_courts, filter_cases, get_case, and 14 more. Their descriptions and schemas cost roughly 4,928 tokens of context every time the server is loaded.
Does the Open Legal Data (Germany) MCP server require authentication?
No. We connected to Open Legal Data (Germany) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Open Legal Data (Germany) MCP server still maintained?
Open Legal Data (Germany) is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Open Legal Data (Germany) MCP server?
VerifyMCP ran 13 checks on Open Legal Data (Germany), covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.