Rechtspraak (Dutch Case Law)
NPM · RECHTSPRAAK-MCP
Dutch case law over MCP: search & fetch uitspraken by ECLI (Rechtspraak Open Data + LiDO)
Available components
Last scanned (11 hours ago)
Scores higher than 92% of npm servers
Category Education and Research
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to Prudai/rechtspraak-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 156 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability68
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1096 tokens (~182/item across 6 items; 6 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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 (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
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.
- 3 Nov 26 0
- Stability: 0.97 → pass security
- 2 Nov 26 0
- Stability: pass → 0.97 functional
- 27 Oct 26 0
- Stability: 0.97 → pass security
- 26 Oct 26 0
- Stability: pass → 0.97 functional
- 24 Oct 26 −2
- CVE-2023-54404 affects this package: high ▼ security
- 23 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 22 Oct 26 0
- Security disclosure: fail → unverified ▼ functional
- 20 Oct 26 0
- Stability: 0.97 → pass security
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 6 Nov 2026 · Analysed npm/rechtspraak-mcp@0.1.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | Prudai/rechtspraak-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/Prudai/rechtspraak-mcp/.github/workflows/publish.yml@refs/tags/v0.1.1 |
| Rekor log index | 1704903044 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:ccbe5fea5dbc60ac2c0c66076053481f30370dda80076658aa52df0c3d7e5575579dde50b143bcea6324efd923f3c875345a098589f6569a2ffe95033 |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 2 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-gh4j-gqv2-49f6 | CVE-2026-41650 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N | yes |
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
get_uitspraak ~171
Fetch the full text and metadata of a single Dutch court decision by ECLI, from the official Open Data API (data.rechtspraak.nl). Returns metadata (court, date, rechtsgebied, zaaknummer), the plain-text body, formal relations (conclusie/cassatie/etc.), and links to the ruling on rechtspraak.nl plus a PrudAI viewer. If the ECLI is not published or has no body text, the tool says so — do not invent or cite it in that case.
| Name | Type | Req | Description |
|---|---|---|---|
| ecli | string | – | ECLI identifier, e.g. ECLI:NL:HR:2023:1234 (alias: id). |
| id | string | – | Alias for ecli. |
| metadataOnly | boolean | – | When true, fetch metadata only (no body text). |
No output schema declared.
No examples provided.
get_uitspraken_bulk ~103
Fetch multiple Dutch court decisions by ECLI in one call (1–10 ECLIs) from the official Open Data API. Returns a per-ECLI result with the body text, metadata, relations, and links — or an error for any ECLI that is unpublished or not found.
| Name | Type | Req | Description |
|---|---|---|---|
| eclis | array | yes | 1–10 ECLI identifiers. |
| metadataOnly | boolean | – | When true, fetch metadata only (no body text). |
No output schema declared.
No examples provided.
lido_related ~240
Get the LiDO citation graph around a Dutch ECLI: rulings that cite it or are cited by it, referenced statute articles, and official publications, with typed Dutch link labels (e.g. 'Verwijst naar', 'Conclusie', 'Vernietigt'). Data comes from KOOP's live LiDO service (linkeddata.overheid.nl). Use it to position a ruling (is it a landmark? what does it cite?). Read-only and bounded (per-direction limit default 100, max 250). This returns structure, not full text — use get_uitspraak for the text of any neighbour.
| Name | Type | Req | Description |
|---|---|---|---|
| direction | string | – | 'both' (default), 'in' (only citing), 'out' (only cited). |
| ecli | string | yes | ECLI identifier, e.g. ECLI:NL:HR:2019:1278. Case-sensitive local segment. |
| limit | integer | – | Per-direction edge limit (default 100). |
| linkTypeCodes | array | – | Optional filter on link-type codes (e.g. ['lx-referentie', 'rvr-conclusie']). |
No output schema declared.
No examples provided.
list_waardelijsten ~113
List the Rechtspraak value lists (waardelijsten) used to build valid search filters: instanties, instanties_buitenlands, rechtsgebieden, proceduresoorten, niet_nederlandse_uitspraken. 'rechtsgebieden' and 'instanties' return the identifiers/URIs you pass to search_uitspraken (rechtsgebied / instanties). Call without a name to see the available lists.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | Which value list to fetch. Omit to list available names. |
No output schema declared.
No examples provided.
search_uitspraken ~323
Search Dutch case law (jurisprudentie/uitspraken) via the official Open Data API and get back ECLIs with links to the ruling and a PrudAI viewer. This is a faceted search: filter by rechtsgebied, instantie, date range and document type. It does not do free-text keyword matching. If you already have an ECLI, pass it as `query` and the tool returns that single decision's summary. Use list_waardelijsten to discover valid rechtsgebied/instantie identifiers.
| Name | Type | Req | Description |
|---|---|---|---|
| dateFrom | string | – | Uitspraakdatum from, YYYY-MM-DD. |
| dateTo | string | – | Uitspraakdatum to, YYYY-MM-DD. |
| from | integer | – | Zero-based pagination offset (default 0). |
| instanties | array | – | Court filter: a single OWMS creator URI (find it via list_waardelijsten). |
| max | integer | – | Max results to return (default 25). |
| query | string | – | A single ECLI to look up directly. (Open Data has no free-text search; non-ECLI keywords are ignored — use the facet filters instead.) |
| rechtsgebied | string | – | Rechtsgebied slug (e.g. 'civielrecht', 'strafrecht', 'bestuursrecht', 'internationaalpubliekrecht') or full PSI URI. |
| sort | string | – | 'date' for newest-first; otherwise the API's default order. |
| type | string | – | Restrict to rulings or AG conclusies. |
No output schema declared.
No examples provided.
search_uitspraken_bulk ~146
Run several Open Data lookups at once (3–10 entries). Pass ECLIs to resolve a batch of decisions' summaries in one call. Note: Open Data has no free-text matching, so non-ECLI terms fall back to facet-only results — prefer get_uitspraken_bulk when you already have the ECLIs. Use to cast a broad net before narrowing down via get_uitspraak.
| Name | Type | Req | Description |
|---|---|---|---|
| from | integer | – | Zero-based offset per term (default 0). |
| pageSize | integer | – | Results per term (max 10, default 10). |
| terms | array | yes | 3–10 distinct search terms, phrased differently. |
No output schema declared.
No examples provided.
How do I install the Rechtspraak (Dutch Case Law) MCP server?
Rechtspraak (Dutch Case Law) runs locally as an npm package, launched with npx -y rechtspraak-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · rechtspraak-mcp
claude mcp add prudai-rechtspraak-mcp -- npx -y rechtspraak-mcp
What is the Rechtspraak (Dutch Case Law) MCP server?
Rechtspraak (Dutch Case Law) is an MCP server listed in the public MCP registry as io.github.Prudai/rechtspraak-mcp. Dutch case law over MCP: search & fetch uitspraken by ECLI (Rechtspraak Open Data + LiDO). This page covers its npm package (rechtspraak-mcp).
Is the Rechtspraak (Dutch Case Law) MCP server safe to use?
Rechtspraak (Dutch Case Law) scores 88 out of 100 on VerifyMCP. We recorded 2 known advisories against it as of 6 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Rechtspraak (Dutch Case Law) MCP server expose?
Rechtspraak (Dutch Case Law) exposes 6 tools: search_uitspraken, search_uitspraken_bulk, get_uitspraak, get_uitspraken_bulk, list_waardelijsten, lido_related. Their descriptions and schemas cost roughly 1,096 tokens of context every time the server is loaded.
Is the Rechtspraak (Dutch Case Law) MCP server still maintained?
Rechtspraak (Dutch Case Law) is still listed as active in the MCP registry. We last reached this channel on 6 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Rechtspraak (Dutch Case Law) MCP server under?
Rechtspraak (Dutch Case Law) declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the Rechtspraak (Dutch Case Law) MCP server?
VerifyMCP ran 16 checks on Rechtspraak (Dutch Case Law), covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.