Louisiana Code
NPM · @PIPEWORX/MCP-LOUISIANA-CODE · 2 COMPONENTS
Louisiana Laws — Revised Statutes, Civil Code, Code of Civil Procedure, Code of Criminal…
Available components
Last scanned (8 hours ago)
Scores higher than 83% 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-louisiana-code). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 19 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability60
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 937 tokens (~312/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 Management80
- Stability observed for 24 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
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
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 →
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.
- 21 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
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 22 Nov 2026 · Analysed npm/@pipeworx/mcp-louisiana-code@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-louisiana-code |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-louisiana-code/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3649726408 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:95eb4a2b4281e2f873a9337be92805aec3c9b5b66dd3b0bca3485fc0c7cc1b658785474ca978719ae38f2580e70925d05a00803fb2a210e4049878ccf |
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 →
louisiana_law_search ~281
Full-text search of Louisiana law BY TOPIC or keyword — "vehicular homicide", "security deposit lessor", "concealed handgun permit", "wrongful death damages" — across the Revised Statutes, Civil Code, Code of Civil Procedure, Code of Criminal Procedure, Code of Evidence, Children's Code and the Louisiana Constitution, optionally narrowed to chosen code bodies. Returns relevance-ranked sections with citation, heading, the date each was last modified, the total match count, and the doc_id to pass to louisiana_statute for full text. The engine ANDs every word, so two or three specific words outperform a sentence. Keyless; sourced live from the Louisiana State Legislature.
| Name | Type | Req | Description |
|---|---|---|---|
| bodies | array | – | Law bodies to search: RS (Revised Statutes), CC (Civil Code), CCP, CCRP, CE, CHC (Children's Code), CONST, CA, HRULE, SRULE, JRULE. Default: all. |
| limit | number | – | Max results to return, default 20, max 100 (the source renders the first 100 of a larger set). |
| query | string | yes | Topic or keywords, e.g. "vehicular homicide". Words are ANDed; "a or b" and "a not b" are understood; ""exact phrase"" in doubled quotes matches in order. |
No output schema declared.
No examples provided.
louisiana_statute ~371
Get the FULL TEXT of one section of Louisiana law by citation — Louisiana Revised Statutes ("RS 14:20" justifiable homicide, "La. R.S. 32:414" driver licence suspension), Civil Code articles ("CC 2315" liability for damages), Code of Civil Procedure ("CCP 966" summary judgment), Code of Criminal Procedure ("CCRP 701" speedy trial), Code of Evidence ("CE 404"), Children's Code ("CHC 603") and the Louisiana Constitution ("Const. Art. I, §5"). Returns the heading, statutory text, the section's enactment and amendment history ("Added by Acts 1976, No. 655; Amended by Acts 2014, No. 163") parsed into year/act pairs, and the legislature's own URL. Keyless; sourced live from the Louisiana State Legislature. Use for "what does Louisiana R.S. 14:20 say", "text of La. Civil Code art. 2315", or to check a Louisiana statute a case or contract cites.
| Name | Type | Req | Description |
|---|---|---|---|
| citation | string | – | The citation as written: "RS 14:20", "La. R.S. 9:2800.1", "14:20" (Revised Statutes), "CC 2315" / "La. C.C. art. 2315" (Civil Code), "CCP 966", "CCRP 701", "CE 404", "CHC 603", "Const. Art. I, §5" or… |
| doc_id | string | – | Alternative to citation: the legis.la.gov document id (the d= number) returned by louisiana_law_search or louisiana_title_contents. |
No output schema declared.
No examples provided.
louisiana_title_contents ~230
List every section in one TITLE of the Louisiana Revised Statutes with its heading and doc_id — Title 14 Criminal Law, Title 32 Motor Vehicles, Title 47 Revenue and Taxation, Title 9 Civil Code Ancillaries — optionally filtered by a word in the heading, so an agent can find the right section when a keyword search is too broad ("every section of Title 14 with 'homicide' in its heading"). Repealed sections are flagged. Keyless; sourced live from the Louisiana State Legislature's table of contents.
| Name | Type | Req | Description |
|---|---|---|---|
| filter | string | – | Optional case-insensitive substring to match in the section heading or citation, e.g. "homicide". |
| limit | number | – | Max sections to return, default 50, max 200. |
| offset | number | – | Skip this many matching sections, default 0 — for paging through a large title. |
| title | string | yes | Revised Statutes title number, e.g. "14" (Criminal Law), "32" (Motor Vehicles), "47" (Revenue and Taxation). |
No output schema declared.
No examples provided.
How do I install the Louisiana Code MCP server?
Louisiana Code runs locally as an npm package, launched with npx -y @pipeworx/mcp-louisiana-code. 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-louisiana-code
claude mcp add pipeworx-io-louisiana-code -- npx -y @pipeworx/mcp-louisiana-code
What is the Louisiana Code MCP server?
Louisiana Code is an MCP server listed in the public MCP registry as io.github.pipeworx-io/louisiana-code. Louisiana Laws, Revised Statutes, Civil Code, Code of Civil Procedure, Code of Criminal… This page covers its npm package (@pipeworx/mcp-louisiana-code).
Is the Louisiana Code MCP server safe to use?
Louisiana Code scores 89 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 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 Louisiana Code MCP server expose?
Louisiana Code exposes 3 tools: louisiana_statute, louisiana_law_search, louisiana_title_contents. Their descriptions and schemas cost roughly 882 tokens of context every time the server is loaded.
Is the Louisiana Code MCP server still maintained?
Louisiana Code is still listed as active in the MCP registry. We last reached this channel on 22 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 Louisiana Code MCP server under?
Louisiana Code 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 Louisiana Code MCP server?
VerifyMCP ran 16 checks on Louisiana Code, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. 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.