Skip to content

Open Legal Data (Germany) MCP server

io.openlegaldata/deopenlegaldata.iostreamable-httpv0.16.5Scanned

German court decisions (Rechtsprechung) and laws (Gesetze) with citation graph and citation checks.

19 tools: 1 do something that can't be undone, 2 change things and 16 only read.

Tools: 0 delete, 1 irreversible, 2 write, 16 read.
  • Reads private data · 0
  • Reads text others write · 1
  • Can send data out · 0
  • 2 findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here does something that can't be undone. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Open Legal Data (Germany) MCP server can do

The Open Legal Data (Germany) MCP server is published by openlegaldata.io, a domain the MCP Registry verified. It has 19 tools. It can do things that cannot be undone, such as sending, paying or publishing (submit_feedback) and create or change data (2 tools: get_court and filter_cases), but cannot delete data. 16 tools only read.

1 tool brings in text other people can write (list_courts).

The fixed checks matched 2 findings (annotation-conflict and long-description). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 10, 2026, version 0.16.5.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

19 tools

Can't be undone 1Claude Code: ask
  • submit_feedbackSend feedback about OLDP or this MCP server to the OLDP team.No findings

    Why it is in this group

    • The name "submit_feedback" says "submit": a word for a change.
    • The description's first verb is "send": a word for sending, and what is sent cannot be taken back.
    Description, as the server wrote it
    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 return an error with a sign-up link. 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": ...}``.

    Annotations the server declares

    • title: Send feedback to OLDP
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
Changes things 2Claude Code: ask
  • filter_casesStructured filtering of court cases using the database.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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. 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).

    Annotations the server declares

    • title: Filter court decisions
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_courtGet detailed information about a specific court.1 finding

    Why it is in this group

    • The name "get_court" says "get": a word for reading.
    • The input takes a statement or command to run (input.code), which can change anything it can reach.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "get_court" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "get_court" says "get": a word for reading.

      What this check looks for
    Description, as the server wrote it
    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-berlin-charlottenburg"). code: Court ECLI code (e.g. "AGBCHAR").

    Annotations the server declares

    • title: Get court details
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 16Show 16 read-only tools
  • get_caseRetrieve a court case by ID or slug.No findings

    Why it is in this group

    • The name "get_case" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Get court decision
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_case_referencesGet forward references FROM a case (what this case cites).No findings

    Why it is in this group

    • The name "get_case_references" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Get references in a decision
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_case_statisticsGet aggregated case statistics.No findings

    Why it is in this group

    • The name "get_case_statistics" says "get": a word for reading.
    Description, as the server wrote it
    Get aggregated case statistics. Returns case counts grouped by time period, optionally filtered by court, state, or jurisdiction. 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: 1 year 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.

    Annotations the server declares

    • title: Get court decision statistics
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_cases_for_lawFind all cases that cite a specific law section.No findings

    Why it is in this group

    • The name "get_cases_for_law" says "get": a word for reading.
    Description, as the server wrote it
    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``.

    Annotations the server declares

    • title: Find decisions citing a law
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_citing_casesGet reverse references TO a case (cases that cite this case).No findings

    Why it is in this group

    • The name "get_citing_cases" says "get": a word for reading.
    Description, as the server wrote it
    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``.

    Annotations the server declares

    • title: Find decisions citing a decision
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_law_sectionGet the full text of a specific law section.No findings

    Why it is in this group

    • The name "get_law_section" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Get law section
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_platform_infoGet OLDP platform coverage summary.No findings

    Why it is in this group

    • The name "get_platform_info" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Get platform coverage
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_server_instructionsReturn MCP server instructions (if any).No findings

    Why it is in this group

    • The name "get_server_instructions" says "get": a word for reading.
    Description, as the server wrote it
    Return MCP server instructions (if any). Always call first.

    Annotations the server declares

    • title: Get server instructions
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_similar_casesFind court cases textually similar to a given case.No findings

    Why it is in this group

    • The name "get_similar_cases" says "get": a word for reading.
    Description, as the server wrote it
    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``.

    Annotations the server declares

    • title: Find similar court decisions
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_courtsBrowse and filter German courts.Reads text others writeNo findings

    Why it is in this group

    • The name "list_courts" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "browse": it reads web pages, which anyone can write.
    Description, as the server wrote it
    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``.

    Annotations the server declares

    • title: List courts
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_law_booksList available German law books (e.g.No findings

    Why it is in this group

    • The name "list_law_books" says "list": a word for reading.
    Description, as the server wrote it
    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. limit: Maximum results (default 50, max 200). Values above 200 are clamped; the response then includes ``limit_clamped: true`` and the original ``requested_limit``.

    Annotations the server declares

    • title: List law books
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • search_casesFull-text search for German court cases via Elasticsearch.1 finding

    Why it is in this group

    • The name "search_cases" says "search": a word for reading.

    Findings

    • Info

      The description is 2,354 characters long, over the 2,000 this check looks for.

      Matched text

      description ends: "...it_clamped: true`` and the original ``requested_limit``."

      What this check looks for
    Description, as the server wrote it
    Full-text search for German court cases via Elasticsearch. Returns matching cases with 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 (e.g. "823"). 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 result also carries ``match_quality`` ("high"/"medium"/"low" relative to the top hit) so you can tell where relevance drops off; it is left out for "date" and "most_cited", where the score is not the ranking signal. limit: Maximum results (default 10, max 50). Values above 50 are clamped; the response then includes ``limit_clamped: true`` and the original ``requested_limit``.

    Annotations the server declares

    • title: Search court decisions
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • search_lawsFull-text search across law sections via Elasticsearch.No findings

    Why it is in this group

    • The name "search_laws" says "search": a word for reading.
    Description, as the server wrote it
    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 (e.g. "BGB"). limit: Maximum results (default 10, max 50). Values above 50 are clamped; the response then includes ``limit_clamped: true`` and the original ``requested_limit``.

    Annotations the server declares

    • title: Search laws
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • validate_citationCheck if a legal citation exists in the OLDP database.No findings

    Why it is in this group

    • The name "validate_citation" says "validate": a word for reading.
    Description, as the server wrote it
    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".

    Annotations the server declares

    • title: Validate legal citation
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • whoamiShow who you are connected as and your remaining request budget.No findings

    Why it is in this group

    • The name "whoami" says "whoami": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Show connection and rate limit
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 18, 2026, 16:21 UTC, unchanged since Nov 11, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
3
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://de.openlegaldata.io/.well-known/oauth-protected-resource/mcp
Authorization servers
https://de.openlegaldata.io
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
no
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 3 tools that change things (1 irreversible, 2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://de.openlegaldata.io/mcp: tools/list returned 19 tools to an anonymous client, including submit_feedback (irreversible), get_court (write), filter_cases (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 warn1 info
  • The server marks "get_court" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "get_court" says "get": a word for reading.

    What this check looks for
  • The description is 2,354 characters long, over the 2,000 this check looks for.

    Matched text

    description ends: "...it_clamped: true`` and the original ``requested_limit``."

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 0.16.5. Values in angle brackets are yours to fill in.

claude mcp add --transport http de https://de.openlegaldata.io/mcp
claude mcp add --transport http de https://de.openlegaldata.io/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__de__get_server_instructions",
      "mcp__de__list_courts",
      "mcp__de__get_case",
      "mcp__de__get_case_statistics",
      "mcp__de__get_similar_cases",
      "mcp__de__search_cases",
      "mcp__de__get_law_section",
      "mcp__de__list_law_books",
      "mcp__de__search_laws",
      "mcp__de__get_case_references",
      "mcp__de__get_cases_for_law",
      "mcp__de__get_citing_cases",
      "mcp__de__validate_citation",
      "mcp__de__get_platform_info",
      "mcp__de__search_legal",
      "mcp__de__whoami"
    ],
    "ask": [
      "mcp__de__get_court",
      "mcp__de__filter_cases",
      "mcp__de__submit_feedback"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as de. Review it before you use it.

Capability tags behind 1 rule
  • mcp__de__list_courts untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.openlegaldata/de/verify?hash=08313061d71924be81c4badeea9ee2243b155eb4ad83b98e8a547845f058e0e7" | jq -e '.changed == false'

Pinned hash 08313061d719, from Nov 10, 2026, 21:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.openlegaldata/de/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.openlegaldata/de
[![Anlyon Radar](https://radar.anlyon.com/badge/io.openlegaldata/de.svg)](https://radar.anlyon.com/servers/io.openlegaldata/de)

Source: MCP Registry · repository. Synced Nov 10, 2026, 21:18 UTC.

Open Legal Data (Germany) MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Open Legal Data (Germany) MCP server safe?

No scan can promise that. What its definitions show: 19 tools, 3 of which can change, send or delete something, and 2 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Open Legal Data (Germany) MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Open Legal Data (Germany) MCP server do things that cannot be undone?

Yes. 1 tool can send, pay, publish or merge: submit_feedback.

What tools does the Open Legal Data (Germany) MCP server have?

19 tools: 1 irreversible, 2 write, 16 read. submit_feedback, get_court, filter_cases, get_server_instructions, list_courts, get_case, get_case_statistics, get_similar_cases and 11 more.

Does the Open Legal Data (Germany) MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Open Legal Data (Germany) MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Open Legal Data (Germany) MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 10, 2026.