Fr Judilibre
NPM · @PIPEWORX/MCP-FR-JUDILIBRE · 2 COMPONENTS
French court decisions (Cour de cassation and the judicial courts under it) — search, read a…
Available components
Last scanned (5 hours ago)
Scores higher than 69% of npm servers
Category Education and Research
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 & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-fr-judilibre). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 3 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability58
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 940 tokens (~313/item across 3 items; 3 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 Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 0
- Security disclosure: unverified → fail ▼ functional
- 2 Nov 26 +2
- Security disclosure: fail → unverified ▼ functional
- Stability: unverified → 0.13 ▲ functional
- Package version: 0.2.0 → 0.2.1 functional
- 31 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 78
First indexed and scored.
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 5 Nov 2026 · Analysed npm/@pipeworx/mcp-fr-judilibre@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-fr-judilibre |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-fr-judilibre/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3637318355 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:029a429cea726ea4cde961d9fe081b130a3a8040fad2713c873f4825839a708d41eb1b4c5c6a26de2432f6bc4c68461df24ecd357f4f69d28f1cc5258 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
fr_judilibre_decision ~157
Read one French judicial decision by id (from fr_judilibre_search): full pseudonymised text, its structural zones (introduction/exposé/moyens/motivations/dispositif/annexes as character offsets into `text`), the texts it applies (`visa`, with best-effort `cited_articles` linking to @pipeworx/france-legi's code+article), related decisions (contested, forward, rapprochements) and attached files.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The decision id, from a fr_judilibre_search result. |
| resolve_references | boolean | – | When true, the source resolves linked decision/text references inline instead of leaving them as bare ids (default false). |
No output schema declared.
No examples provided.
fr_judilibre_search ~489
Search French judicial decisions (Cour de cassation and the courts of appeal it indexes) published as open data: full-text `query` plus filters for jurisdiction, chamber, formation, decision type, theme, publication level and solution, paged. Returns decision ids, summaries and highlighted snippets; fr_judilibre_decision reads the full text. Codes like "cc" (jurisdiction) or "civ1" (chamber) resolve to French labels via fr_judilibre_taxonomy.
| Name | Type | Req | Description |
|---|---|---|---|
| chamber | array | – | Chamber codes, e.g. "civ1", "soc", "comm", "crim". See fr_judilibre_taxonomy(id:"chamber"). |
| date_end | string | – | Decision date range end, ISO YYYY-MM-DD. |
| date_start | string | – | Decision date range start, ISO YYYY-MM-DD. |
| field | array | – | Restrict the full-text match to these decision zones, e.g. ["motivations","dispositif"]. Omit to search the whole decision. |
| formation | array | – | Formation codes (bench size/type). See fr_judilibre_taxonomy(id:"formation"). |
| jurisdiction | array | – | Jurisdiction codes, e.g. "cc" (Cour de cassation), "ca" (cour d'appel). See fr_judilibre_taxonomy(id:"jurisdiction"). |
| page | number | – | 0-based page number (default 0). |
| page_size | number | – | Results per page, 1-50 (default 10). |
| publication | array | – | Publication-level codes, e.g. "b" (Bulletin), "r" (Rapport). See fr_judilibre_taxonomy(id:"publication"). A decision with none of these is unpublished — most are. |
| query | string | – | Full-text search terms, e.g. "responsabilité du fait des choses". |
| solution | array | – | Outcome codes, e.g. "rejet", "cassation". See fr_judilibre_taxonomy(id:"solution"). |
| theme | array | – | Subject-matter theme codes. See fr_judilibre_taxonomy(id:"theme"). |
| type | array | – | Decision type codes, e.g. "arret" (judgment), "qpc" (constitutionality question). See fr_judilibre_taxonomy(id:"type"). |
No output schema declared.
No examples provided.
fr_judilibre_taxonomy ~238
Resolve the short codes fr_judilibre_search/fr_judilibre_decision use (jurisdiction, chamber, formation, type, solution, publication, theme) into their French labels, or the reverse (a label into its code). Pass no `id` to list the available taxonomy categories.
| Name | Type | Req | Description |
|---|---|---|---|
| context_value | string | – | Context needed by some categories — e.g. "chamber" only makes sense within a jurisdiction: context_value:"cc" for the Cour de cassation's chambers (the default), "ca" for a cour d'appel's. |
| id | string | – | Taxonomy category, e.g. "jurisdiction", "chamber", "formation", "type", "solution", "publication", "theme". Omit to list the categories. |
| key | string | – | A code within `id` to resolve to its label, e.g. id:"jurisdiction", key:"cc" -> "Cour de cassation". Requires `id`. |
| value | string | – | A label within `id` to resolve back to its code (the reverse of `key`). Requires `id`. |
No output schema declared.
No examples provided.
How do I install the Fr Judilibre MCP server?
Fr Judilibre runs locally as an npm package, launched with npx -y @pipeworx/mcp-fr-judilibre. 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-judilibre
claude mcp add pipeworx-io-fr-judilibre -- npx -y @pipeworx/mcp-fr-judilibre
What is the Fr Judilibre MCP server?
Fr Judilibre is an MCP server listed in the public MCP registry as io.github.pipeworx-io/fr-judilibre. French court decisions (Cour de cassation and the judicial courts under it), search, read a… This page covers its npm package (@pipeworx/mcp-fr-judilibre).
Is the Fr Judilibre MCP server safe to use?
Fr Judilibre scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Judilibre MCP server expose?
Fr Judilibre exposes 3 tools: fr_judilibre_search, fr_judilibre_decision, fr_judilibre_taxonomy. Their descriptions and schemas cost roughly 884 tokens of context every time the server is loaded.
Is the Fr Judilibre MCP server still maintained?
Fr Judilibre is still listed as active in the MCP registry. We last reached this channel on 5 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 Judilibre MCP server under?
Fr Judilibre declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.