Skip to main content
Glama

nl-eli-mcp

Install (one command)

As a Claude plugin (Claude Code or the desktop app, needs uv); see plugin/README.md for what it sends and stores:

/plugin marketplace add matematicsolutions/nl-eli-mcp
/plugin install nl-eli-mcp@nl-eli-mcp

Published on PyPI + MCP Registry (io.github.matematicsolutions/nl-eli-mcp). Run without cloning:

uvx nl-eli-mcp

Configure your MCP client (stdio):

{ "mcpServers": { "nl-eli-mcp": { "command": "uvx", "args": ["nl-eli-mcp"] } } }

Windows 11 with Smart App Control

Smart App Control blocks unsigned executables, which covers uvx.exe, pip.exe and the nl-eli-mcp.exe launcher that pip writes at install time. The python.exe and py.exe from the python.org installer are signed by the Python Software Foundation, so running the module through the interpreter works:

python -m pip install nl-eli-mcp
python -m nl_eli_mcp

pip.exe is blocked for the same reason, so install with python -m pip, not pip install. If python is not on PATH, use the Windows launcher: py -3 -m nl_eli_mcp.

{ "mcpServers": { "nl-eli-mcp": { "command": "python", "args": ["-m", "nl_eli_mcp"] } } }

Do not turn Smart App Control off to work around this - it cannot be re-enabled without reinstalling Windows.

Building from source: see Install.

An MCP server for the Dutch consolidated legislation BWB (Basiswettenbestand), served by KOOP over the official SRU API (zoekservice.overheid.nl, keyless). It gives an AI agent the version of an act in force on a given date, with a verifiable citation: a persistent identifier, a human-readable citation, and a link to the official source.

Part of the eu-legal-mcp line by MateMatic — one connector per EU member state, the same citation contract everywhere.

On ELI. The Netherlands does not publish native ELI (/eli/) URIs on consolidated BWB. To keep the line's contract honest, eli_uri carries the official persistent identifier instead — the wetten.overheid.nl/id toestand URI (e.g. http://wetten.overheid.nl/id/BWBR0005537/2026-06-04/0). The connector never fabricates an /eli/ URI and says so in its tool instructions. See DISCOVERY.md.

Related MCP server: Agent.ai MCP Server

Tools

Tool

What it does

nl_search(query, on_date=today)

Find acts by words in the title that are in force on a date. Returns distinct acts, each with the citation contract.

nl_get_act(bwb_id, on_date=today)

Metadata for one act (e.g. BWBR0005537) — identifier, title, authority, version date.

nl_get_text(bwb_id, on_date=today)

The full consolidated XML (BWB toestand) of one act.

nl_case_search(date_from, date_to, ...)

List court decisions (Rechtspraak Open Data) by date range / court / subject. No free-text; each hit carries a native ecli.

nl_get_decision(ecli)

A court decision by its ECLI (e.g. ECLI:NL:HR:2020:1) — court, dates, zaaknummer and full text.

nl_coverage()

Declare what this connector covers, when each family was captured, and - explicitly - what it does NOT cover. Every gap carries a fallback.

Legislation comes from the BWB (KOOP SRU); case law comes from Rechtspraak Open Data (data.rechtspraak.nl), keyed by native ECLI. Every response carries the citation contract:

  • eli_uri — the official persistent identifier (toestand URI; see the ELI note above).

  • human_readable_citation — the official short title (citeertitel), e.g. Algemene wet bestuursrecht.

  • source_url — the browsable wetten.overheid.nl page for that version.

Versions and dates

Each act has many time-stamped versions. The tools default to the version in force today; pass on_date (YYYY-MM-DD) to pin a historical or future version. An act with no version valid on that date returns not_found — retry with another on_date.

Install

pip install -e ".[dev]"

Register it with your MCP client (see .mcp.json.example):

{
  "mcpServers": {
    "nl-eli-mcp": {
      "command": "nl-eli-mcp",
      "env": {
        "NL_ELI_BASE_URL": "https://zoekservice.overheid.nl/sru/Search",
        "NL_ELI_CACHE_DIR": "~/.matematic/cache/nl-eli",
        "NL_ELI_AUDIT_DIR": "~/.matematic/audit"
      }
    }
  }
}

Design

  • Public data only. Read-only against the keyless KOOP SRU API, the official repository host and Rechtspraak Open Data; nothing is sent beyond the query / identifier and the date.

  • Audit log. Every call appends one JSON line to ~/.matematic/audit/nl-eli-mcp.jsonl (record-keeping).

  • Network. Besides the sources above, once on first use the server fetches a small configuration file (nl-runtime.json.gz, updated source addresses) from this repository's GitHub Releases. That request carries no query content; GitHub's download counter for the file is the only usage signal we see. NL_ELI_RUNTIME_URL="" turns it off; the Claude plugin ships with it off. No LLM provider, no other telemetry; own backoff + on-disk cache.

  • No fabrication. Identifiers and titles are parsed from the source record. If KOOP's schema changes, the connector fails loudly rather than returning stale or invented data.

See CONSTITUTION.md (the 4 principles) and DISCOVERY.md (how the source was mapped).

Tests

pytest tests/test_instructions_drift.py tests/test_parse.py   # offline
pytest tests/test_smoke.py                                     # live KOOP API

Licence

Apache-2.0. The Dutch legislation served is official public data of the Kingdom of the Netherlands; this connector adds no rights over it.

Available Tools

6 tools
nl_coverageA
Read-onlyIdempotent

Declare what this connector covers, how it is sourced, and what it does NOT cover.

Call this before telling a user that the law "does not contain" something, and whenever a search comes back empty: the absence may be a gap in this connector rather than in the law. Every gap carries a fallback saying where to look instead.

Returns: Coverage with families, an as-of note, and a non-empty list of known gaps.

Inputs: no named parameters. Returns: What this connector covers, how it is sourced, and what it does not cover.

nl_get_actA
Read-onlyIdempotent

Fetch metadata for the version of a Dutch act in force on a date.

Inputs: bwb_id (required), on_date. Returns: A Dutch consolidated act (one toestand / version), parsed from a KOOP SRU gzd r…

nl_get_decisionA
Read-onlyIdempotent

Fetch a Dutch court decision by its ECLI (Rechtspraak Open Data).

Inputs: ecli (required). Returns: Result of ``nl_get_decision`` - a Dutch court decision with native ECLI.

nl_get_textA
Read-onlyIdempotent

Fetch the full consolidated XML of a Dutch act in force on a date.

Inputs: bwb_id (required), on_date. Returns: Result of ``nl_get_text`` (full consolidated XML of one version).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.2/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool targets a clearly distinct operation: searching acts, fetching act metadata, fetching act text, searching cases, fetching a specific decision, and describing coverage. There is no realistic overlap that could lead an agent to pick the wrong tool.

    Naming Consistency4/5

    All tools share the nl_ prefix, which creates a recognizable namespace, but the internal pattern is not uniform: nl_get_* uses verb-first naming, while nl_case_search is object-first and nl_coverage is a bare noun. This is a minor inconsistency rather than a confusing mix.

    Tool Count5/5

    Six tools is well-scoped for a legal information connector covering both legislation and case law. Each tool serves a necessary retrieval or orientation purpose, and none feels redundant.

    Completeness5/5

    The set covers search, metadata retrieval, and full-text retrieval for acts, plus metadata-based search and full-decision retrieval for case law. The dedicated coverage tool explicitly documents limitations and fallbacks, which closes the main practical gap in legal data connectors.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      An intelligent MCP server that enables AI agents to crawl, index, and semantically search official framework documentation using local RAG. It prevents hallucinations by providing precise, up-to-date documentation excerpts directly into the AI's context window.
      1
      -
    • A
      license
      C
      quality
      D
      maintenance
      An MCP server that integrates with the Agent.ai API to provide web text extraction, web screenshots, and YouTube transcript capabilities through a dynamic function loading system.
      100
      4
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that provides tools to fetch live, version-accurate documentation, changelogs, examples, and method signatures for npm and PyPI packages, preventing AI coding agents from hallucinating stale APIs.
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      This MCP server provides LLMs with a live, curated knowledge base of AI agent research, world models, and source-code reviews, enabling personalized and context-aware responses. Users can either connect to the hosted knowledge or build and host their own vault.
      -