fr-eli-mcp 0.1.0__tar.gz

fr_eli_mcp-0.1.0/.github/workflows/release.yml

@@ -0,0 +1,58 @@
+name: release
+
+# Trusted publishing to PyPI via GitHub OIDC (no API token stored) + MCP Registry.
+# Trigger: push a version tag, e.g. `git tag v0.1.0 && git push origin v0.1.0`.
+
+on:
+  push:
+    tags:
+      - "v*"
+  workflow_dispatch: {}   # manual re-run of the MCP Registry publish without bumping the package version
+
+permissions:
+  contents: read
+  id-token: write   # required for PyPI trusted publishing (OIDC) and registry login
+
+jobs:
+  build-and-publish-pypi:
+    if: github.event_name == 'push'   # only on a version tag; skipped on manual dispatch
+    runs-on: ubuntu-latest
+    environment: pypi
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Set up Python
+        uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+
+      - name: Install build tooling
+        run: python -m pip install --upgrade build
+
+      - name: Build sdist + wheel
+        run: python -m build
+
+      - name: Publish to PyPI (trusted publishing, no token)
+        uses: pypa/gh-action-pypi-publish@release/v1
+
+  publish-mcp-registry:
+    needs: build-and-publish-pypi
+    # run after a successful PyPI publish, OR standalone on manual dispatch
+    if: always() && (github.event_name == 'workflow_dispatch' || needs.build-and-publish-pypi.result == 'success')
+    runs-on: ubuntu-latest
+    permissions:
+      contents: read
+      id-token: write   # OIDC login to the MCP Registry
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Install mcp-publisher
+        run: |
+          curl -L "https://github.com/modelcontextprotocol/registry/releases/latest/download/mcp-publisher_$(uname -s | tr '[:upper:]' '[:lower:]')_amd64.tar.gz" | tar xz mcp-publisher
+          sudo mv mcp-publisher /usr/local/bin/
+
+      - name: Login to MCP Registry (GitHub OIDC)
+        run: mcp-publisher login github-oidc
+
+      - name: Publish server.json to MCP Registry
+        run: mcp-publisher publish

fr_eli_mcp-0.1.0/.gitignore

@@ -0,0 +1,27 @@
+# Python
+.venv/
+__pycache__/
+*.py[cod]
+*.egg-info/
+dist/
+build/
+.pytest_cache/
+.mypy_cache/
+.ruff_cache/
+
+# Secrets / local config (NEVER source) - PISTE OAuth credentials live here
+.env
+.mcp.json
+
+# Local runtime (never source)
+.matematic/
+*.log
+
+# Live API probe scratch (raw dumps - not part of the package)
+_probe/
+
+# OS
+.DS_Store
+Thumbs.db
+
+# Note: tests/fixtures/* ARE committed - public Legifrance data needed for offline tests.

fr_eli_mcp-0.1.0/.mcp.json.example

@@ -0,0 +1,16 @@
+{
+  "mcpServers": {
+    "fr-eli-mcp": {
+      "command": "fr-eli-mcp",
+      "env": {
+        "FR_ELI_ENV": "sandbox",
+        "FR_ELI_OAUTH_URL": "https://sandbox-oauth.piste.gouv.fr/api/oauth/token",
+        "FR_ELI_BASE_URL": "https://sandbox-api.piste.gouv.fr/dila/legifrance/lf-engine-app",
+        "FR_ELI_CLIENT_ID": "REPLACE_WITH_YOUR_PISTE_CLIENT_ID",
+        "FR_ELI_CLIENT_SECRET": "REPLACE_WITH_YOUR_PISTE_CLIENT_SECRET",
+        "FR_ELI_CACHE_DIR": "~/.matematic/cache/fr-eli",
+        "FR_ELI_AUDIT_DIR": "~/.matematic/audit"
+      }
+    }
+  }
+}

fr_eli_mcp-0.1.0/.publication-gate.json

@@ -0,0 +1,4 @@
+{
+  "_comment": "Test fixtures hold public Legifrance ids whose digits can trip the PL-aware checksum heuristics. Allow the fixtures dir. pubgate:allow",
+  "allow_paths": ["tests/fixtures/"]
+}

fr_eli_mcp-0.1.0/CONSTITUTION.md

@@ -0,0 +1,65 @@
+# Constitution of fr-eli-mcp
+
+Version: 0.1.0
+Date: 2026-06-24
+Licence: Apache-2.0
+
+`fr-eli-mcp` is an MCP server for the French Legifrance API exposed through PISTE
+(`piste.gouv.fr`). It searches consolidated legislation (LODA laws & decrees, codes) and case law
+(JURI), returning verifiable citations. Unlike the keyless connectors in this line, Legifrance
+requires OAuth2 credentials.
+
+The 4 principles below are inherited from the `eu-legal-mcp` line Constitution (Article IV).
+
+---
+
+## Art. 1. Public data only
+
+Legifrance is the official, public source of French law. The server is read-only against the
+Legifrance API and sends nothing beyond the search query / document id it is asked for. The OAuth2
+credentials authenticate the *application*, not an end user, and are read from the environment only
+(`FR_ELI_CLIENT_ID` / `FR_ELI_CLIENT_SECRET`) - never hard-coded, never logged.
+
+## Art. 2. Mandatory audit log
+
+Every tool call MUST append one JSON line to `~/.matematic/audit/fr-eli-mcp.jsonl`
+(ts / tool / input_hash SHA-256 / output_count_or_size / duration_ms / status). Inability to write =
+the tool returns an error, it does not silently skip.
+
+## Art. 3. Vendor neutrality
+
+No tool hardcodes an LLM provider, assumes a model, or adds commercial telemetry. The server talks
+only to the PISTE OAuth + Legifrance endpoints and the local filesystem. The OAuth token is cached
+in process memory only (never persisted to disk) and refreshed on expiry or on a 401.
+
+## Art. 4. ELI / ECLI citations and a human-readable citation are mandatory
+
+Every response MUST carry the citation contract:
+- `eli_uri`: a **stable, resolvable Legifrance resource URL**. The PISTE `lf-engine-app` consult
+  API returns the native `eli` / `idEli` fields *null* for legislation, so we DO NOT synthesize a
+  `/eli/...` string from prose - we carry the CID-keyed legifrance.gouv.fr URL that resolves, and we
+  say so (`eli_note`). Rule of the line: **state what you do not have; never fabricate an ELI.**
+- `human_readable_citation`: the French citation convention (e.g. "LOI n° 2016-1321 du 7 octobre
+  2016 pour une République numérique"; "Code civil, art. 9"; the JURI title for a decision).
+- `source_url`: the legifrance.gouv.fr page for the item.
+- For case law, `ecli` carries the **native, authoritative ECLI** returned by the API
+  (e.g. `ECLI:FR:CCASS:2025:C100399`) - cited verbatim, never invented.
+
+---
+
+## Open points
+
+1. **ELI** - if/when the PISTE API (or a dedicated ELI endpoint) exposes a populated native ELI for
+   legislation, `eli_uri` should switch to it. Until then it is the resolvable CID-keyed URL.
+2. **Distribution** - Legifrance requires a PISTE key, so this connector ships via the PATRON /
+   appliance channel (governed), not casual drop-in download (see the line's distribution note).
+3. **Sandbox vs production** - the defaults target the PISTE *sandbox*. Production uses the
+   `oauth.piste.gouv.fr` / `api.piste.gouv.fr` hosts (set via `FR_ELI_OAUTH_URL` / `FR_ELI_BASE_URL`).
+4. **Coverage** - MVP covers LODA + codes + JURI consult. Other fonds (JORF, CETAT, CONSTIT, KALI)
+   are later features.
+
+## Constitution evolution
+
+Changes to art. 1-4 follow SEMVER + an entry in `CHANGELOG.md` + a `pyproject.toml` bump.
+
+First version: 2026-06-24. Author: Wieslaw Mazur / MateMatic.

fr_eli_mcp-0.1.0/DISCOVERY.md

@@ -0,0 +1,61 @@
+# Discovery - fr-eli-mcp (Legifrance via PISTE)
+
+Date: 2026-06-24. Decision: **BUILD** (sandbox fully working: token + subscription + live data).
+
+## Source
+
+- **API:** Legifrance, exposed through PISTE (`piste.gouv.fr`). Base (sandbox):
+  `https://sandbox-api.piste.gouv.fr/dila/legifrance/lf-engine-app`.
+- **Auth:** OAuth2 `client_credentials`. Token endpoint (sandbox):
+  `https://sandbox-oauth.piste.gouv.fr/api/oauth/token`. Body params
+  `grant_type=client_credentials` + `client_id` + `client_secret` + `scope=openid` →
+  `access_token` (`token_type=Bearer`, `expires_in=3600`, scope `openid resource.READ`).
+- **Production:** swap the sandbox hosts for `oauth.piste.gouv.fr` / `api.piste.gouv.fr`.
+
+Registration (account + API subscription + ToS acceptance) is a one-time human act on the PISTE
+portal; it was completed before this build. The connector itself is fully autonomous thereafter.
+
+## Probed live (not trusted from docs)
+
+All endpoints are `POST` JSON under the base, with a `Bearer` token.
+
+- `POST /search` - `{fond, recherche:{champs[…], filtres[…], pageNumber, pageSize, operateur, sort,
+  typePagination}}`. Verified for `fond` ∈ {`LODA_DATE`, `CODE_DATE`, `JURI`}. `LODA_DATE` /
+  `CODE_DATE` require a `DATE_VERSION` `singleDate` (epoch ms) filter. Results:
+  `results[].titles[]{id, cid, title}` + `nature` / `origin` / `etat`; `CODE_DATE` results also
+  carry `sections[].extracts[]{id (LEGIARTI…), num, values}`.
+- `POST /consult/lawDecree` - `{textId (LEGITEXT…), date (YYYY-MM-DD)}` → full LODA text with
+  `id`, `cid` (JORFTEXT…), `title`, `nor`, `nature`, `dateParution`, nested `sections[].articles[]`.
+- `POST /consult/getArticle` - `{id (LEGIARTI…)}` → `article{id, num, texte, etat, dateDebut,
+  textTitles[] (carries the code title, e.g. "Code civil"), fullSectionsTitre}`.
+- `POST /consult/juri` - `{textId (JURITEXT…)}` → `text{id, ecli, juridiction, formation, solution,
+  numeroAffaire, dateTexte, titre, texte}`.
+
+### Key finding - ELI is null, ECLI is native
+
+For LODA texts and code articles the API returns `eli` / `idEli` / `idEliAlias` **null**, and there
+are no `/eli/…` strings anywhere in the consult payloads. The act number ("2016-1321") and signature
+date are only present inside the `title` prose string (`textNumber` / `dateTexte` are null on the
+LODA consult). Per the line rule we therefore do **not** fabricate a `/eli/…` URI from prose; we
+carry the stable, resolvable CID-keyed legifrance.gouv.fr URL as `eli_uri`.
+
+JURI is different: `text.ecli` is a populated, authoritative ECLI (e.g. `ECLI:FR:CCASS:2025:C100399`).
+This makes `fr-eli-mcp` the first connector in the line to surface a native ECLI straight from the
+source API.
+
+## Citation contract mapping
+
+| Field | LODA / code article | JURI |
+| --- | --- | --- |
+| `eli_uri` | `https://www.legifrance.gouv.fr/loda/id/{LEGITEXT}` / `…/codes/article_lc/{LEGIARTI}` (resolvable, CID-keyed; **not** a native ELI) | `https://www.legifrance.gouv.fr/juri/id/{JURITEXT}` |
+| `human_readable_citation` | the `title` prose ("LOI n° … du …") / "Code civil, art. 9" | the decision `titre` |
+| `source_url` | same legifrance.gouv.fr page | same |
+| `ecli` | - | native `text.ecli` |
+
+## Build
+
+3 reuse-verbatim modules (`audit.py`, `cache.py` - env `FR_ELI_*`, log `fr-eli-mcp.jsonl`), and the
+FR-specific `client.py` (OAuth2 + in-memory token cache + 401 refresh + POST JSON), `citations.py`,
+`models.py`, `server.py` (4 tools, `ToolError` {invalid_arg / not_found / upstream_error /
+config_error}). Tests: offline drift + offline fixture parse + live smoke. The factory holds: the
+infrastructure is reused, only the source adapter is new.

fr_eli_mcp-0.1.0/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

fr_eli_mcp-0.1.0/PKG-INFO

@@ -0,0 +1,108 @@
+Metadata-Version: 2.4
+Name: fr-eli-mcp
+Version: 0.1.0
+Summary: MCP server for the French Legifrance API via PISTE (legifrance.gouv.fr) — search legislation (LODA, codes) and case law (JURI) with verifiable citations and native ECLI.
+Project-URL: Repository, https://github.com/matematicsolutions/fr-eli-mcp
+Project-URL: Issues, https://github.com/matematicsolutions/fr-eli-mcp/issues
+Project-URL: Homepage, https://matematic.co
+Author-email: Matematic Solutions <kontakt@matematic.co>, Wieslaw Mazur <mazur.wieslaw2022@gmail.com>
+License: Apache-2.0
+License-File: LICENSE
+Keywords: ecli,eli,france,law,legaltech,legifrance,mcp,piste
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Legal Industry
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Topic :: Office/Business
+Requires-Python: >=3.11
+Requires-Dist: anyio>=4.3
+Requires-Dist: diskcache>=5.6
+Requires-Dist: fastmcp>=0.2.0
+Requires-Dist: httpx>=0.27
+Requires-Dist: pydantic>=2.6
+Provides-Extra: dev
+Requires-Dist: mypy>=1.10; extra == 'dev'
+Requires-Dist: pytest-asyncio>=0.23; extra == 'dev'
+Requires-Dist: pytest>=8.0; extra == 'dev'
+Requires-Dist: ruff>=0.5; extra == 'dev'
+Description-Content-Type: text/markdown
+
+# fr-eli-mcp
+
+<!-- mcp-name: io.github.matematicsolutions/fr-eli-mcp -->
+
+An MCP server for the **French Legifrance API** via [PISTE](https://piste.gouv.fr). It searches
+French legislation (LODA laws & decrees, codes) and case law (JURI), and returns verbatim text with
+verifiable citations. Part of the **eu-legal-mcp** line of national legal connectors by
+[MateMatic](https://matematic.co).
+
+Every response carries the citation contract: a stable `eli_uri`, a `human_readable_citation`
+(French convention) and a resolvable `source_url`.
+
+> **Read-only.** The server only queries Legifrance and writes a local audit log. It never modifies
+> official text and never sends anything beyond your query / document id.
+
+## Tools
+
+| Tool | What it does |
+| --- | --- |
+| `fr_search(query, fond, page_size)` | Keyword search a `fond`: `LODA` (laws & decrees), `CODE` (codes), `JURI` (case law). Returns hits with the citation contract; `CODE` hits expose matched `article_id`s. |
+| `fr_get_act(text_id, date)` | Consult a LODA law/decree by `LEGITEXT...` id. Returns metadata + a table of contents (`articles`). |
+| `fr_get_text(article_id)` | Verbatim text of a single article by `LEGIARTI...` id. |
+| `fr_get_decision(decision_id)` | A JURI court decision by `JURITEXT...` id, with its **native `ecli`**, court, formation, solution and text. |
+
+### A note on ELI vs ECLI
+
+France has an official ELI scheme, but the PISTE `lf-engine-app` **consult API returns the native
+ELI field `null` for the legislation we tested**. Following this line's rule - *say what you do not
+have, never fabricate an ELI* - `eli_uri` carries the **stable, resolvable Legifrance resource URL**
+(CID-keyed), not a `/eli/...` string parsed from prose. Each response repeats this in `eli_note`.
+
+Case law is different: the API returns a **native, authoritative ECLI**
+(e.g. `ECLI:FR:CCASS:2025:C100399`), surfaced verbatim in `fr_get_decision`.
+
+## Configuration
+
+Legifrance requires OAuth2 application credentials from a free PISTE account
+(`piste.gouv.fr` → *Applications* → subscribe to the Legifrance API → *OAuth Credentials*).
+Credentials are read from the environment only:
+
+| Variable | Meaning |
+| --- | --- |
+| `FR_ELI_OAUTH_URL` | OAuth token endpoint (sandbox default shown in `.mcp.json.example`). |
+| `FR_ELI_BASE_URL` | Legifrance `lf-engine-app` base. |
+| `FR_ELI_CLIENT_ID` | Your PISTE application client id (**required**). |
+| `FR_ELI_CLIENT_SECRET` | Your PISTE application client secret (**required**). |
+| `FR_ELI_CACHE_DIR` | Disk cache dir (default `~/.matematic/cache/fr-eli`). |
+| `FR_ELI_AUDIT_DIR` | Audit log dir (default `~/.matematic/audit`). |
+
+Copy `.mcp.json.example` to `.mcp.json` (gitignored) and fill in your credentials, or set the
+variables in your host environment. The OAuth token is cached in memory and refreshed automatically.
+
+## Install
+
+```bash
+py -3.13 -m venv .venv
+.\.venv\Scripts\python.exe -m pip install -e ".[dev]"   # Windows
+# or: python -m pip install -e ".[dev]"                  # POSIX
+```
+
+## Tests
+
+```bash
+pytest tests/test_instructions_drift.py tests/test_parse.py   # offline, no creds
+pytest tests/test_smoke.py -v                                 # live, needs PISTE creds in .env
+```
+
+## Distribution
+
+Because Legifrance requires a PISTE key, this connector is distributed through the **PATRON /
+appliance** channel (governed), not casual drop-in download. See the eu-legal-mcp line notes.
+
+## Licence
+
+Apache-2.0. Legifrance content is © the French Republic / DILA and subject to the Legifrance /
+PISTE terms of use; this software only retrieves and cites it.

fr_eli_mcp-0.1.0/README.md

@@ -0,0 +1,76 @@
+# fr-eli-mcp
+
+<!-- mcp-name: io.github.matematicsolutions/fr-eli-mcp -->
+
+An MCP server for the **French Legifrance API** via [PISTE](https://piste.gouv.fr). It searches
+French legislation (LODA laws & decrees, codes) and case law (JURI), and returns verbatim text with
+verifiable citations. Part of the **eu-legal-mcp** line of national legal connectors by
+[MateMatic](https://matematic.co).
+
+Every response carries the citation contract: a stable `eli_uri`, a `human_readable_citation`
+(French convention) and a resolvable `source_url`.
+
+> **Read-only.** The server only queries Legifrance and writes a local audit log. It never modifies
+> official text and never sends anything beyond your query / document id.
+
+## Tools
+
+| Tool | What it does |
+| --- | --- |
+| `fr_search(query, fond, page_size)` | Keyword search a `fond`: `LODA` (laws & decrees), `CODE` (codes), `JURI` (case law). Returns hits with the citation contract; `CODE` hits expose matched `article_id`s. |
+| `fr_get_act(text_id, date)` | Consult a LODA law/decree by `LEGITEXT...` id. Returns metadata + a table of contents (`articles`). |
+| `fr_get_text(article_id)` | Verbatim text of a single article by `LEGIARTI...` id. |
+| `fr_get_decision(decision_id)` | A JURI court decision by `JURITEXT...` id, with its **native `ecli`**, court, formation, solution and text. |
+
+### A note on ELI vs ECLI
+
+France has an official ELI scheme, but the PISTE `lf-engine-app` **consult API returns the native
+ELI field `null` for the legislation we tested**. Following this line's rule - *say what you do not
+have, never fabricate an ELI* - `eli_uri` carries the **stable, resolvable Legifrance resource URL**
+(CID-keyed), not a `/eli/...` string parsed from prose. Each response repeats this in `eli_note`.
+
+Case law is different: the API returns a **native, authoritative ECLI**
+(e.g. `ECLI:FR:CCASS:2025:C100399`), surfaced verbatim in `fr_get_decision`.
+
+## Configuration
+
+Legifrance requires OAuth2 application credentials from a free PISTE account
+(`piste.gouv.fr` → *Applications* → subscribe to the Legifrance API → *OAuth Credentials*).
+Credentials are read from the environment only:
+
+| Variable | Meaning |
+| --- | --- |
+| `FR_ELI_OAUTH_URL` | OAuth token endpoint (sandbox default shown in `.mcp.json.example`). |
+| `FR_ELI_BASE_URL` | Legifrance `lf-engine-app` base. |
+| `FR_ELI_CLIENT_ID` | Your PISTE application client id (**required**). |
+| `FR_ELI_CLIENT_SECRET` | Your PISTE application client secret (**required**). |
+| `FR_ELI_CACHE_DIR` | Disk cache dir (default `~/.matematic/cache/fr-eli`). |
+| `FR_ELI_AUDIT_DIR` | Audit log dir (default `~/.matematic/audit`). |
+
+Copy `.mcp.json.example` to `.mcp.json` (gitignored) and fill in your credentials, or set the
+variables in your host environment. The OAuth token is cached in memory and refreshed automatically.
+
+## Install
+
+```bash
+py -3.13 -m venv .venv
+.\.venv\Scripts\python.exe -m pip install -e ".[dev]"   # Windows
+# or: python -m pip install -e ".[dev]"                  # POSIX
+```
+
+## Tests
+
+```bash
+pytest tests/test_instructions_drift.py tests/test_parse.py   # offline, no creds
+pytest tests/test_smoke.py -v                                 # live, needs PISTE creds in .env
+```
+
+## Distribution
+
+Because Legifrance requires a PISTE key, this connector is distributed through the **PATRON /
+appliance** channel (governed), not casual drop-in download. See the eu-legal-mcp line notes.
+
+## Licence
+
+Apache-2.0. Legifrance content is © the French Republic / DILA and subject to the Legifrance /
+PISTE terms of use; this software only retrieves and cites it.

fr_eli_mcp-0.1.0/glama.json

@@ -0,0 +1,4 @@
+{
+  "$schema": "https://glama.ai/mcp/schemas/server.json",
+  "maintainers": ["mazurwieslaw2022-cmd"]
+}