Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Fr Legifrance

NPM · @PIPEWORX/MCP-FR-LEGIFRANCE · 2 COMPONENTS

France's Légifrance API via the state's PISTE gateway — the parts @pipeworx/france-legi does NOT…

68 Trust /100

Last scanned (21 hours ago)

Scores higher than 39% of npm servers

Category Education and Research

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency45
Schema Quality & AI Usability62
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 915 tokens (~228/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

What we tested

Checks we ran (15)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 16 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 15 Nov 26 53

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Analysed npm/@pipeworx/mcp-fr-legifrance@0.1.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 4 exposed · ~859 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
fr_legifrance_convention_collective ~169

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 fr_legifrance_search(fond:"KALI").

NameTypeReqDescription
_apiKeystringyesPISTE OAuth2 credentials as "client_id:client_secret" for an application subscribed to the "Légifrance Beta" API product. Different from fr-judilibre's KeyId.
idccstringyesThe convention's IDCC identification number, e.g. "1261".

No output schema declared.

No examples provided.

fr_legifrance_journal_officiel_recent ~132

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.

NameTypeReqDescription
_apiKeystringyesPISTE OAuth2 credentials as "client_id:client_secret" for an application subscribed to the "Légifrance Beta" API product. Different from fr-judilibre's KeyId.
nnumber–Number of recent issues to return, 1-30 (default 5).

No output schema declared.

No examples provided.

fr_legifrance_search ~314

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 (CONSTIT), circulaires (CIRC), company-level agreements (ACCO) and CNIL decisions (CNIL). One fond per call. For consolidated codes/LODA use @pipeworx/france-legi; for Cour de cassation judicial case law use @pipeworx/fr-judilibre.

NameTypeReqDescription
_apiKeystringyesPISTE OAuth2 credentials as "client_id:client_secret" for an application subscribed to the "Légifrance Beta" API product. Different from fr-judilibre's KeyId.
date_endstring–Decision date range end, ISO YYYY-MM-DD. Only applied for fond CETAT/CONSTIT.
date_startstring–Decision date range start, ISO YYYY-MM-DD. Only applied for fond CETAT/CONSTIT.
fondstringyesWhich corpus to search.
pagenumber–1-based page number (default 1).
page_sizenumber–Results per page, 1-50 (default 10).
querystringyesFull-text search terms, e.g. "licenciement économique" or "convention collective métallurgie".

No output schema declared.

No examples provided.

fr_legifrance_text ~244

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 has no prefixed id, just a number), pass fond:"CIRC". Refuses a JURITEXT id (Cour de cassation) and a LEGITEXT/LEGIARTI id (codes/LODA), naming the sibling pack that serves those.

NameTypeReqDescription
_apiKeystringyesPISTE OAuth2 credentials as "client_id:client_secret" for an application subscribed to the "Légifrance Beta" API product. Different from fr-judilibre's KeyId.
fondstring–Only needed to read a circulaire by its bare numeric id, which has no recognisable prefix.
idstringyesThe text id, from a fr_legifrance_search result, or a bare circulaire number.

No output schema declared.

No examples provided.

Install

How do I install the Fr Legifrance MCP server?

Fr Legifrance runs locally as an npm package, launched with npx -y @pipeworx/mcp-fr-legifrance. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @pipeworx/mcp-fr-legifrance

# add to Claude Code
claude mcp add pipeworx-io-fr-legifrance -- npx -y @pipeworx/mcp-fr-legifrance
Common questions

What is the Fr Legifrance MCP server?

Fr Legifrance is an MCP server listed in the public MCP registry as io.github.pipeworx-io/fr-legifrance. France's Légifrance API via the state's PISTE gateway, the parts @pipeworx/france-legi does NOT… This page covers its npm package (@pipeworx/mcp-fr-legifrance).

Is the Fr Legifrance MCP server safe to use?

Fr Legifrance scores 68 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Fr Legifrance MCP server expose?

Fr Legifrance exposes 4 tools: fr_legifrance_search, fr_legifrance_text, fr_legifrance_journal_officiel_recent, fr_legifrance_convention_collective. Their descriptions and schemas cost roughly 859 tokens of context every time the server is loaded.

Is the Fr Legifrance MCP server still maintained?

Fr Legifrance is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Fr Legifrance MCP server under?

Fr Legifrance declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the Fr Legifrance MCP server?

VerifyMCP ran 15 checks on Fr Legifrance, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about Fr Legifrance: Stability. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.