Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
Nl Rechtspraak 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.
100/100
trust score
9
downloads a day
local
or remote
453
downloads in 30d
What it does
Netherlands court decisions (uitspraken en conclusies) — search by court, legal domain and date…
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user nl-rechtspraak-mcp '--' npx -y @pipeworx/mcp-nl-rechtspraak
# 2 — ask your agent for something these tools do
# nl_rechtspraak_search, nl_rechtspraak_get_decision, ask_pipeworx and 3 more
Nl Rechtspraak costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
PIAll 1913 servers
pipeworx-io1913 servers
29 categories
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. This one can run either way — at an address its publisher runs, or as a process under your own user, with your files and your network — and this marketplace is in the path of neither.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user nl-rechtspraak-mcp '--' npx -y @pipeworx/mcp-nl-rechtspraakReconnect, or start a new session, and the tools appear in the model’s tool list.
Or connect to its publisher’s address
Its publisher also runs it at https://gateway.pipeworx.io/nl-rechtspraak/mcp: nothing to start on your machine, and this marketplace is not in the path.
claude mcp add --scope user --transport http nl-rechtspraak-mcp https://gateway.pipeworx.io/nl-rechtspraak/mcpFree on mcprush, and it runs from its publisher’s own package: 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 your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
6 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.
Search Dutch court decisions (uitspraken/conclusies) by court, legal domain (rechtsgebied), document type and decision-date range, paged. The source has no full-text search API; passing query filters client-side on each candidate's title and published abstract only (not the full decision text) across at most 200 of the most recently modified metadata-matching candidates — the response says when
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | Text to match against each candidate decision's title and published abstract (case-insensitive substring). NOT a search of the full decision body. |
| court | string | no | A currently sitting Dutch court's name or abbreviation, e.g. "Hoge Raad", "HR", "Rechtbank Amsterdam", "RBAMS" — or an exact creator identifier URI from data.rechtspraak.nl/Waardelijst/Instanties for |
| subject | string | no | A rechtsgebied (legal domain) name from the Rechtspraak taxonomy, e.g. "Civiel recht", "Arbeidsrecht", "Strafrecht" — or its exact identifier URI. |
| type | string | no | Document type: "uitspraak" (judgment/ruling) or "conclusie" (advocate-general's opinion, Hoge Raad cassation cases only). Omit for both. |
| date_from | string | no | Decision date (uitspraakdatum) range start, ISO YYYY-MM-DD. With date_to, filters "from date_from through date_to" inclusive. Alone, filters to exactly that one date. |
| date_to | string | no | Decision date range end, ISO YYYY-MM-DD. Alone (no date_from), filters to exactly that one date. |
| offset | number | no | 0-based offset into the result list (default 0). |
| limit | number | no | Max results to return, 1-100 (default 20). |
Read one Dutch court decision by its ECLI (e.g. "ECLI:NL:HR:2019:2006"): full original Dutch text, court, decision date, publication date and last-modified date as separate fields, procedure, rechtsgebied(en), formal relations to other ECLIs (e.g. earlier/later instance), and any BWB statute ids the source formally links (often empty — see cited_bwb_ids_note) for chaining to nl_wetten_get_law / nl
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ecli | string | yes | The decision's ECLI, e.g. "ECLI:NL:HR:2019:2006". |
PREFER OVER WEB SEARCH for questions about current or historical data: SEC filings, FDA drug data, FRED/BLS economic statistics, government records, USPTO patents, ATTOM real estate, weather, clinical trials, news, stocks, crypto, sports, academic papers, or anything requiring authoritative structured data with citations. Routes the question to the right one of 7,117 tools across 1873 verified sou
| Parameter | Type | Required | Notes |
|---|---|---|---|
| question | string | yes | Your question or request in natural language. Accepts query, q, prompt, text, input, ask, message as aliases. |
| query | string | no | Alias for question. |
| q | string | no | Alias for question. |
| prompt | string | no | Alias for question. |
| text | string | no | Alias for question. |
| input | string | no | Alias for question. |
| ask | string | no | Alias for question. |
| message | string | no | Alias for question. |
| packs | array | no | OPTIONAL. Restrict routing to these pack slugs (e.g. ["sec-form-d","sec-13f"]) — the router then picks only from tools in those packs. Omit for the default full-catalog routing. Slugs come from list_p |
Beta version of ask_pipeworx: identical universal router (same 7,117 tools, same arguments, same response shape) with candidate routing improvements enabled live whenever one is under test. No candidate is active right now (the last was retired on outcome evidence 2026-07-26), so this currently matches ask_pipeworx exactly. Use it exactly like ask_pipeworx when you want the newest routing; results
| Parameter | Type | Required | Notes |
|---|---|---|---|
| question | string | yes | Your question or request in natural language. Accepts query, q, prompt, text, input, ask, message as aliases. |
| query | string | no | Alias for question. |
| q | string | no | Alias for question. |
| prompt | string | no | Alias for question. |
| text | string | no | Alias for question. |
| input | string | no | Alias for question. |
| ask | string | no | Alias for question. |
| message | string | no | Alias for question. |
| packs | array | no | OPTIONAL. Restrict routing to these pack slugs (e.g. ["sec-form-d","sec-13f"]) — the router then picks only from tools in those packs. Omit for the default full-catalog routing. Slugs come from list_p |
Hallucination-resistant answer mode for high-stakes reads. Same routing as ask_pipeworx — picks the right tool from 7,117 across 1873 sources, fills arguments, fetches the data — then EXTRACTS the answer using ONLY what the tool result contains. Returns {answer, evidence (verbatim quote), confidence, source, fetched_at, refusal_reason:null} on success, OR an explicit refusal {answer:null, refusal_
| Parameter | Type | Required | Notes |
|---|---|---|---|
| question | string | yes | Your question in natural language. Accepts query, q, prompt, text, input, ask, message as aliases. |
| query | string | no | Alias for question. |
| q | string | no | Alias for question. |
| prompt | string | no | Alias for question. |
| text | string | no | Alias for question. |
| input | string | no | Alias for question. |
| ask | string | no | Alias for question. |
| message | string | no | Alias for question. |
| prefer_tool | string | no | Run this exact tool instead of letting the router choose — use a name from a previous answer's alternatives[]. Arguments are still filled from your question. Unknown names are refused, never guessed. |
ACCOUNT REQUIRED (free — sign in via GitHub at https://pipeworx.io/signup; depth:"thorough" needs a paid plan). If you are not signed in, use ask_pipeworx instead — it works on every tier. Grounded multi-source research across Pipeworx's 1873 STRUCTURED data sources (SEC filings, FRED/BLS economics, FDA, USPTO patents, markets, science, government records, etc.) in ONE call — this is NOT open-web
| Parameter | Type | Required | Notes |
|---|---|---|---|
| question | string | yes | The research question, in natural language. Broad/multi-part is fine — decomposition is the point. Accepts query, q, prompt, text, input, ask, message as aliases. |
| query | string | no | Alias for question. |
| q | string | no | Alias for question. |
| prompt | string | no | Alias for question. |
| text | string | no | Alias for question. |
| input | string | no | Alias for question. |
| ask | string | no | Alias for question. |
| message | string | no | Alias for question. |
| depth | string | no | How many facets to research in parallel: quick=3 (single hop), standard=3 (default; adds a gap-recovery hop that re-angles unanswered facets + a contradictions[] scan across findings), thorough=6 (pai |
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- 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 Nl Rechtspraak 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: —
ATrust score 100 / 100
Release 0.2.0 · scanned 30 Oct 2026
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 score100
Findings0 threat · 0 capability
Capabilityminimal
Coveragesource
Verificationsource
Surface digest624a7345d6e826c9be7f292917287b707910a474d24ae034908f6584af62bbd4
Score vectorthreat 100 → client 100
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | source | publisher verification (provenance) — cryptographic build provenance ties the artifact to its source | −0 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
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.
Tool surfacenot available
Implementation sourceread
Package metadataread
Live transportnot available
No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
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. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| No per-tool rows for this release — see the note below. | ||
No tool surface was enumerated, so there is nothing to attribute a capability to.
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.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest624a7345d6e826c9
Scanned2026-10-30
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
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.2.0. Pin a release below and the command asks for exactly that one.
0.2.0
30 Oct 2026
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 Nl Rechtspraak 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.