@pipeworx/nl-wetten

Connect: https://pipeworx.io/mcp — every tool in the catalog, including @pipeworx/nl-wetten’s. Install: one-click buttons

No MCP client? Skip the connection: POST https://gateway.pipeworx.io/v1/tools/search_packs {"query":"..."} to find a tool below, GET /v1/tools/<name> for its schema, POST the same URL with arguments for the data — see For AI agents.

Tools: 3

Dutch national legislation, consolidated and point-in-time: search by title, look up a regulation’s structure by its BWB id, and read one article’s original Dutch text as it stood on any date.

Tools

• nl_wetten_search(query, as_of?, limit?) — title search over Dutch national legislation; returns the regulation(s) matching, each resolved to the version in force on as_of (default today), with its BWB id (BWBR...). Title search only, not full-text search.
• nl_wetten_get_law(bwb_id, as_of?, offset?, limit?) — one regulation’s citeertitel, authority, legal domain(s), the resolved version’s own validity period, its chapter structure, and a paged list of article numbers (never truncated silently — has_more/next_offset).
• nl_wetten_get_article(bwb_id, article, as_of?) — one article’s original Dutch text, broken into its numbered “lid” (paragraph) subdivisions, plus the date that exact text took effect and the resolved version’s validity period. Pass an earlier as_of to read a past version of the same article.

Every date returned is a separate field: as_of (what you asked for), toestand_valid_from / toestand_valid_until (how long the resolved consolidated version has applied), and — on nl_wetten_get_article — article_in_force_since (when that article’s own text last changed), which can differ from the toestand’s own start date when the article itself hasn’t been amended since an earlier date.

Auth

Keyless.

Data sources

• KOOP (the Dutch government’s publications agency), Basiswettenbestand (BWB) — the consolidated register of Dutch national legislation, covering every statute, AMvB, ministerial regulation and treaty KOOP publishes.

Notes

• The upstream 406s without an explicit Accept: application/xml header. No Accept header at all (what a bare fetch() sends) and Accept: application/json both get HTTP 406, even for an otherwise well-formed, healthy query. Every request this pack makes sets the header.
• A title search without a validity-date filter returns one record per historical version, not per law — “Algemene wet bestuursrecht” alone comes back 40+ times across its amendment history. Every search here adds the as-of date so each regulation resolves to exactly one version.
• Article full text has no JSON form. The consolidated text is only published as XML, and a single law’s document can run several MB (the Algemene wet bestuursrecht’s current version is ~2.6 MB). There’s no XML parser in the Workers runtime, so article text is extracted with targeted pattern matching over the register’s fixed element structure — correct for real statute text, not a general-purpose XML parser.
• Article numbers follow the source’s own numbering, which is not always plain integers — e.g. “1:3” (chapter:article) or “3:9a” (a lettered insertion). Use the exact string nl_wetten_get_law lists.

Tools

• nl_wetten_search — Search Dutch national legislation by title (the BWB Basiswettenbestand). Matches the cite-title and official/unofficial titles as a phrase and returns the regulation(s) in force on “as_of” (default to
• nl_wetten_get_law — Look up one Dutch regulation by its BWB id (e.g. “BWBR0005537”) as it stood on “as_of” (default today): citeertitel, authority, legal domain(s), the toestand’s own validity period (separate from publi
• nl_wetten_get_article — Read the original Dutch text of one article/section of a Dutch regulation, by BWB id and article number (e.g. “1:3”, as listed by nl_wetten_get_law), as it read on “as_of” (default today). Returns the