fi-eli-mcp
# fi-eli-mcp
<!-- mcp-name: io.github.matematicsolutions/fi-eli-mcp -->
## Install (one command)
Published on PyPI + MCP Registry (`io.github.matematicsolutions/fi-eli-mcp`). Run without cloning:
```bash
uvx fi-eli-mcp
```
Configure your MCP client (stdio):
```json
{ "mcpServers": { "fi-eli-mcp": { "command": "uvx", "args": ["fi-eli-mcp"] } } }
```
### Windows 11 with Smart App Control
Smart App Control blocks unsigned executables, which covers `uvx.exe`, `pip.exe`
and the `fi-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 fi-eli-mcp
python -m fi_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 fi_eli_mcp`.
```json
{ "mcpServers": { "fi-eli-mcp": { "command": "python", "args": ["-m", "fi_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](#install).
An MCP server for the Finnish **Finlex** open-data API (`opendata.finlex.fi`). It fetches
consolidated Finnish statutes as Akoma Ntoso 3.0 XML, with verifiable ELI identifiers and
Finnish citations.
Part of the MateMatic `eu-legal-mcp` production line - after PL, DE, AT and ES. Same citation
contract, Finlex source.
> **Scope.** This MVP covers Finnish statutes (saadokset). Discovery is by year (`fi_list_acts`)
> or by year + number; the open-data API is path-based, not keyword search. Finland is bilingual,
> so titles may be Finnish or Swedish. Every response carries a `dataset_note`.
>
> **Licence.** Finnish legislation in Finlex 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 |
|---|---|
| `fi_list_acts` | List the statutes of a year (discovery). |
| `fi_get_act` | Metadata for a statute by year + number. |
| `fi_get_text` | Full Akoma Ntoso text of a statute by year + number. |
| `fi_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.
`http://data.finlex.fi/eli/sd/2018/1050/alkup`), `human_readable_citation`
(e.g. `Tietosuojalaki (1050/2018)`), and `source_url`.
## Install
```bash
cd fi-eli-mcp
pip install -e .
```
## Configure (Claude Code / any MCP client)
```json
{
"mcpServers": {
"fi-eli-mcp": { "command": "fi-eli-mcp" }
}
}
```
Environment:
- `FI_ELI_BASE_URL` - default `https://opendata.finlex.fi/finlex/avoindata/v1`
- `FI_ELI_CACHE_DIR` - default `~/.matematic/cache/fi-eli`
- `FI_ELI_AUDIT_DIR` - default `~/.matematic/audit`
No API key. Finlex open data is keyless.
## Governance
- **Public data only** - read-only against Finlex; no client data leaves the machine.
- **Audit log** - every tool call appends one JSON line to `~/.matematic/audit/fi-eli-mcp.jsonl`.
- **Vendor-neutral** - talks only to `opendata.finlex.fi`; 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 -v # offline
pytest tests/test_smoke.py -v # hits live Finlex
```
## Licence
Apache-2.0. © Matematic Solutions / Wieslaw Mazur.
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: listing statutes by year, fetching metadata, fetching full text, and declaring coverage gaps. There is no overlap or ambiguity between them.
Three tools follow a consistent verb_noun pattern (fi_list_acts, fi_get_act, fi_get_text), but fi_coverage is a noun-only name that breaks the pattern. The inconsistency is minor and doesn't cause confusion.
With 4 tools, the server is small but well-scoped for a focused legal data connector. The count is slightly below the typical range but each tool serves a necessary function in retrieval and transparent coverage reporting.
The tool surface covers core read operations (list, get metadata, get text) plus explicit coverage handling, which is a thoughtful safeguard. A keyword search or version history would be a natural addition but its absence is not a critical gap for the apparent purpose.