Alabama Code
NPM · @PIPEWORX/MCP-ALABAMA-CODE · 2 COMPONENTS
Code of Alabama 1975 — state statutes by citation and by topic. Fleet #2752. Query-arg fix: fleet…
Available components
Last scanned (2 hours ago)
Scores higher than 72% 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-alabama-code). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 5 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability65
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 476 tokens (~238/item across 2 items; 2 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
- Security disclosure: unverified → fail ▼ functional
- Stability: unverified → 0.03 ▲ functional
- Package version: 0.2.0 → 0.2.1 functional
- 29 Oct 26 79
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-alabama-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-alabama-code |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-alabama-code/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3587896748 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:752e9831d2bd94f4ec872a68aa57e545f5fbb17657489c36dc55636e4dcbf14b2dd1f482b0eaf8bf15fee728030fab02dadb90f762617f1acce1f9fc0 |
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 →
al_search ~146
Search the Code of Alabama 1975 BY TOPIC or keyword rather than citation — "landlord security deposit", "concealed pistol permit", "homicide". This is a REAL FULL-TEXT search over actual section body text (not just captions) run live against the Alabama Legislature's own search index — confirmed to surface sections whose title never mentions the search term. Returns matching citations, titles and a text snippet; call al_statute with a citation for the full text. Keyless.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max results to return, default 10, max 25. |
| query | string | yes | Topic or keywords, e.g. "landlord security deposit". |
No output schema declared.
No examples provided.
al_statute ~276
Get the FULL TEXT of a section of the Code of Alabama 1975 — Alabama state law — by citation. "13A-6-2" is murder; "35-9A-204" covers a landlord's duty to maintain the premises. Accepts natural forms: "13A-6-2", "Ala. Code 13A-6-2", "§ 13A-6-2". Returns the current statutory text, section title, the Legislature's own amendment-history citation list (`amendment_history`), and — when an Act has already been enacted but is not yet in force — a forward-looking `pending_version` with its future effective date. Alabama publishes CURRENT text only going backward, so a pre-amendment (historical) version of the text is not available; this tool says so rather than guessing. Keyless. Use for "what does Ala. Code 13A-6-2 say" or to check an Alabama statute a case or lease relies on.
| Name | Type | Req | Description |
|---|---|---|---|
| citation | string | yes | Section citation, title-chapter-section, e.g. "13A-6-2" (murder) or "35-9A-204" (landlord duty to maintain premises). Titles can carry a letter, e.g. "13A". |
No output schema declared.
No examples provided.
How do I install the Alabama Code MCP server?
Alabama Code runs locally as an npm package, launched with npx -y @pipeworx/mcp-alabama-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-alabama-code
claude mcp add pipeworx-io-alabama-code -- npx -y @pipeworx/mcp-alabama-code
What is the Alabama Code MCP server?
Alabama Code is an MCP server listed in the public MCP registry as io.github.pipeworx-io/alabama-code. Code of Alabama 1975, state statutes by citation and by topic. Fleet #2752. Query-arg fix: fleet… This page covers its npm package (@pipeworx/mcp-alabama-code).
Is the Alabama Code MCP server safe to use?
Alabama Code scores 82 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 Alabama Code MCP server expose?
Alabama Code exposes 2 tools: al_statute, al_search. Their descriptions and schemas cost roughly 422 tokens of context every time the server is loaded.
Is the Alabama Code MCP server still maintained?
Alabama Code 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 Alabama Code MCP server under?
Alabama 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.