nl_rechtspraak_search
Pack: nl-rechtspraak · Connect: https://pipeworx.io/mcp (see Connect below for a single-pack URL)
No MCP client? Call it directly: GET https://gateway.pipeworx.io/v1/tools/nl_rechtspraak_search for the schema, then POST the same URL with its arguments for the data.
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 that scan was partial. Returns ECLIs that nl_rechtspraak_get_decision resolves to the full text.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
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 a discontinued court. |
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). |
Example call
Arguments
{
"court": "HR",
"subject": "Civiel recht",
"date_from": "2019-12-19",
"date_to": "2019-12-21",
"query": "klimaat"
}
curl
curl -X POST https://gateway.pipeworx.io/nl-rechtspraak/mcp \
-H 'Content-Type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"nl_rechtspraak_search","arguments":{"court":"HR","subject":"Civiel recht","date_from":"2019-12-19","date_to":"2019-12-21","query":"klimaat"}}}'
TypeScript (@pipeworx/sdk)
import { Pipeworx } from '@pipeworx/sdk';
const pipeworx = new Pipeworx();
const result = await pipeworx.call('nl_rechtspraak_search', {
"court": "HR",
"subject": "Civiel recht",
"date_from": "2019-12-19",
"date_to": "2019-12-21",
"query": "klimaat"
});
Connect
Add this to your MCP client config — every tool in the catalog, including this one — or use one-click install buttons:
{
"mcpServers": {
"pipeworx": {
"url": "https://pipeworx.io/mcp"
}
}
}
Connect to just the nl-rechtspraak pack
{
"mcpServers": {
"nl-rechtspraak": {
"url": "https://gateway.pipeworx.io/nl-rechtspraak/mcp"
}
}
}
See Getting Started for client-specific install steps.