dk-eli-mcp
# dk-eli-mcp
<!-- mcp-name: io.github.matematicsolutions/dk-eli-mcp -->
An MCP server for the Danish **Retsinformation** legal database (`retsinformation.dk`). It
fetches Danish legislation as LexDania 2.1 XML behind native ELI URIs, with verifiable
citations.
Part of the MateMatic `eu-legal-mcp` production line - after PL, DE, AT, ES, FI, IE, NL, SE, FR
and LU. Same citation contract, Retsinformation source. Denmark is ELI-native: every document
has a stable `data.europa.eu/eli`-typed identifier exposed as a `retsinformation.dk/eli/...` URL.
> **Scope.** This MVP grounds Danish documents by ELI coordinate (`year` + `number` in the `lta`
> collection = Lovtidende A) or by accession number, and lists documents changed on a date. The
> API is path-based, not keyword search. It covers laws (LOV), consolidated laws (LBK), executive
> orders (BEK), circulars (CIR) and guidelines (VEJ). Language: Danish. Every response carries a
> `dataset_note`.
>
> **Licence of the data.** Danish legislation in Retsinformation is official public information
> published as Open Data (keyless). This connector relays it with attribution and a `source_url`.
## The tools
| Tool | What it does |
|---|---|
| `dk_get_act` | Metadata for a document by year + number, or by accession. |
| `dk_get_text` | Full LexDania XML of a document (verbatim official text). |
| `dk_recent_changes` | Documents changed on a given date (harvest API). |
| `dk_coverage` | Declare what this connector covers, when each family was captured, and - explicitly - what it does NOT cover. Every gap carries a fallback. |
Every response carries the contract: `eli_uri` (a full ELI URL, e.g.
`https://www.retsinformation.dk/eli/lta/2018/502`), `human_readable_citation`
(e.g. `Databeskyttelsesloven (LOV nr. 502 af 23/05/2018)`), and `source_url`.
## Install
Run it with no install step (once published to PyPI):
```bash
uvx dk-eli-mcp
```
Or from source:
```bash
cd dk-eli-mcp
pip install -e .
```
## Configure (Claude Code / any MCP client)
```json
{
"mcpServers": {
"dk-eli-mcp": { "command": "dk-eli-mcp" }
}
}
```
### Windows 11 with Smart App Control
Smart App Control blocks unsigned executables, which covers `uvx.exe`, `pip.exe`
and the `dk-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:
```bash
python -m pip install dk-eli-mcp
python -m dk_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 dk_eli_mcp`.
```json
{ "mcpServers": { "dk-eli-mcp": { "command": "python", "args": ["-m", "dk_eli_mcp"] } } }
```
Do not turn Smart App Control off to work around this - it cannot be re-enabled
without reinstalling Windows.
Environment:
- `DK_ELI_BASE_URL` - default `https://www.retsinformation.dk`
- `DK_ELI_API_URL` - default `https://api.retsinformation.dk` (harvest API)
- `DK_ELI_CACHE_DIR` - default `~/.matematic/cache/dk-eli`
- `DK_ELI_AUDIT_DIR` - default `~/.matematic/audit`
No API key. Retsinformation open data is keyless.
> The harvest API behind `dk_recent_changes` is only available 03:00-23:45 Danish time. Outside
> that window the tool returns an `upstream_error`; an empty list during the window means nothing
> changed on that date.
## Governance
- **Public data only** - read-only against Retsinformation; no client data leaves the machine.
- **Audit log** - every tool call appends one JSON line to `~/.matematic/audit/dk-eli-mcp.jsonl`.
- **Vendor-neutral** - talks only to `retsinformation.dk`; no LLM provider, no telemetry.
- **Verifiable citations** - every response is independently checkable via `source_url`.
See `CONSTITUTION.md` and `DISCOVERY.md`.
## Tests
```bash
pip install -e ".[dev]"
pytest tests/test_instructions_drift.py tests/test_parse.py -v # offline
pytest tests/test_smoke.py -v # hits live Retsinformation
```
## Licence
Apache-2.0. © Matematic Solutions / Wieslaw Mazur.
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: metadata retrieval, full-text retrieval, coverage declaration, and change listing. No two tools overlap in what they return, making misselection unlikely.
All tools share the dk_ prefix, and most follow a verb_noun pattern (dk_get_act, dk_get_text). dk_coverage and dk_recent_changes deviate slightly by using nouns rather than verbs, but the pattern remains readable and predictable.
With four tools, the set is compact but sufficient for its narrow scope. It could benefit from a search tool, but the count is reasonable and each tool earns its place.
The core needs are covered: fetch metadata, fetch full text, list recent changes, and explicitly declare coverage gaps. Minor gaps exist—such as no search-by-keyword or version-history tool—but the dk_coverage tool mitigates uncertainty and provides fallbacks.