MCP server for Chelaile realtime bus data
Fr Legifrance is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
France's Légifrance API via the state's PISTE gateway — the parts @pipeworx/france-legi does NOT…
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user fr-legifrance-mcp '--' npx -y @pipeworx/mcp-fr-legifrance
# 2 — ask your agent for something these tools do
# fr_legifrance_search, fr_legifrance_text, fr_legifrance_journal_officiel_recent and 1 more
Fr Legifrance costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one can run either way — at an address its publisher runs, or as a process under your own user, with your files and your network — and this marketplace is in the path of neither.
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user fr-legifrance-mcp '--' npx -y @pipeworx/mcp-fr-legifranceReconnect, or start a new session, and the tools appear in the model’s tool list.
Its publisher also runs it at https://gateway.pipeworx.io/fr-legifrance/mcp: nothing to start on your machine, and this marketplace is not in the path.
claude mcp add --scope user --transport http fr-legifrance-mcp https://gateway.pipeworx.io/fr-legifrance/mcpNothing is required, but it can take PIPEWORX_API_KEY (Optional Pipeworx API key. Without it calls are anonymous and capped daily; a free key raises the cap.) if you want to set it.
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
4 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
Full-text search across French legal sources the Légifrance API serves beyond codes and Cour de cassation case law: the Journal officiel (fond JORF), collective-bargaining agreements (KALI), Conseil d'État / administrative case law (CETAT, the JADE dataset), Constitutional Council decisions…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| fond | string | yes | Which corpus to search. |
| query | string | yes | Full-text search terms, e.g. "licenciement économique" or "convention collective métallurgie". |
| date_start | string | no | Decision date range start, ISO YYYY-MM-DD. Only applied for fond CETAT/CONSTIT. |
| date_end | string | no | Decision date range end, ISO YYYY-MM-DD. Only applied for fond CETAT/CONSTIT. |
| page | number | no | 1-based page number (default 1). |
| page_size | number | no | Results per page, 1-50 (default 10). |
| _apiKey | string | yes | PISTE OAuth2 credentials as "client_id:client_secret" for an application subscribed to the "Légifrance Beta" API product. Different from fr-judilibre's KeyId. |
Read one full text by id from fr_legifrance_search's results: a JORFTEXT (Journal officiel), KALITEXT/KALIARTI/KALICONT (collective agreement text/article/container), CETATEXT (Conseil d'État decision), CONSTEXT (Constitutional Council decision), CNILTEXT or ACCOTEXT id. For a circulaire (which…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | The text id, from a fr_legifrance_search result, or a bare circulaire number. |
| fond | string | no | Only needed to read a circulaire by its bare numeric id, which has no recognisable prefix. |
| _apiKey | string | yes | PISTE OAuth2 credentials as "client_id:client_secret" for an application subscribed to the "Légifrance Beta" API product. Different from fr-judilibre's KeyId. |
List the most recently published issues of the Journal officiel de la République française, each with its id, publication date, JO number and the texts it contains. A text id inside an issue can be read with fr_legifrance_text.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| n | number | no | Number of recent issues to return, 1-30 (default 5). |
| _apiKey | string | yes | PISTE OAuth2 credentials as "client_id:client_secret" for an application subscribed to the "Légifrance Beta" API product. Different from fr-judilibre's KeyId. |
Resolve a collective-bargaining agreement by its IDCC number (e.g. "1261") to its title, scope and the KALITEXT ids of its base texts — the entry point for KALI when you have an IDCC rather than a raw text id. Read a returned base_text_id with fr_legifrance_text; find amendments by keyword with…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| idcc | string | yes | The convention's IDCC identification number, e.g. "1261". |
| _apiKey | string | yes | PISTE OAuth2 credentials as "client_id:client_secret" for an application subscribed to the "Légifrance Beta" API product. Different from fr-judilibre's KeyId. |
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Fr Legifrance or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| No per-tool rows for this release — see the note below. | ||
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.1.0. Pin a release below and the command asks for exactly that one.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Fr Legifrance can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.