# Arkansas Code (npm · @pipeworx/mcp-arkansas-code)

Arkansas Code of 1987 — state statutes by citation and by topic search. Fleet #2881, closing the…

- Trust score: 82/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 84/100, [markdown](https://verifymcp.io/servers/pipeworx-io-arkansas-code/arkansas-code-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-arkansas-code/arkansas-code-mcp)
- npm · `@pipeworx/mcp-arkansas-code`: 82/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-arkansas-code/pipeworx-mcp-arkansas-code.md), [page](https://verifymcp.io/servers/pipeworx-io-arkansas-code/pipeworx-mcp-arkansas-code)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-arkansas-code`
- Version: `0.2.1`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-arkansas-code).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 5 days ago).
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 63/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 569 tokens (~284/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Arkansas Code MCP server?

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

### Claude

```bash
claude mcp add pipeworx-io-arkansas-code -- npx -y @pipeworx/mcp-arkansas-code
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-arkansas-code": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-arkansas-code"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-arkansas-code": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-arkansas-code"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-arkansas-code -- npx -y @pipeworx/mcp-arkansas-code
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-arkansas-code": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-arkansas-code"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-arkansas-code --command npx --arg -y --arg @pipeworx/mcp-arkansas-code
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-arkansas-code:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-arkansas-code"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-arkansas-code": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-arkansas-code"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-arkansas-code -t stdio -c npx -a -y @pipeworx/mcp-arkansas-code
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-arkansas-code": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-arkansas-code"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 82, 0)

- [functional regression] Security disclosure: fail → unverified

### 2026-11-04 (score 82, +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.

### 2026-11-03 (score 81, 0)

- [functional regression] Security disclosure: unverified → fail

### 2026-11-02 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-01 (score 80, 0)

- [functional regression] Security disclosure: fail → unverified

### 2026-10-31 (score 80, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-10-30 (score 64, −15)

- [security regression] Malware scan: pass → unverified
- [functional regression] Security disclosure: unverified → fail
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-10-29 (score 79)

First indexed and scored.

## MCP tools (2)

### `ar_statute` (~354 tokens)

Get the TEXT of a section of the Arkansas Code (Ark. Code Ann.) by citation — state statutes, e.g. "5-10-101" (capital murder), "4-70-101". Accepts natural forms: "5-10-101", "Ark. Code Ann. 5-10-101", "ACA § 5-10-101". Returns the catchline, the operative statutory text, the "History." line (the Acts that enacted/amended it), and other legislative notes when present — case-law annotations are deliberately excluded (can run to hundreds of KB per heavily-litigated section). SOURCED FROM A 2020-11-06 RELEASE OF A PUBLIC-DOMAIN SOURCE — the official LexisNexis portal requires passing an authentication/CAPTCHA wall, so this is the newest free, non-walled text found; every response carries data_as_of and a staleness warning. Also returns later_acts: a dated, linked overlay of every act the Arkansas legislature's OWN Code-Sections-Amended index shows touching this exact citation since the 2020-11-06 snapshot (act number, session, PDF link) — NOT merged into the text, explicitly labelled so, with sessions_checked naming every session the index covers even when later_acts is empty. Use for "what does ACA 5-10-101 say" or to check an Arkansas statute AND whether it has been amended since 2020-11-06. Keyless.

Input parameters:

- `citation` (string, required): Section citation, title-chapter-section, e.g. "5-10-101" or "Ark. Code Ann. 4-70-101".

### `ar_search` (~160 tokens)

Search the Arkansas Code BY TOPIC or keyword over official section catchlines (section titles), not citation — e.g. "capital murder", "security deposit", "concealed carry". Returns matching citations and catchlines; call ar_statute with a citation for the full text. Catchline search only (not full statutory- text search) — a query that never appears in any catchline will return no matches even if the underlying topic is discussed inside a section's body. Sourced from the same 2020-11-06 release as ar_statute. Keyless.

Input parameters:

- `limit` (number): Max results to return, default 10, max 50.
- `query` (string, required): Topic or keywords, e.g. "security deposit".

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-arkansas-code/pipeworx-mcp-arkansas-code#diagnostics

## Score history

- 2026-11-05: 82
- 2026-11-04: 82
- 2026-11-03: 81
- 2026-11-02: 81
- 2026-11-01: 80
- 2026-10-31: 80
- 2026-10-30: 64
- 2026-10-29: 79

## Common questions

### What is the Arkansas Code MCP server?

Arkansas Code is an MCP server listed in the public MCP registry as io.github.pipeworx-io/arkansas-code. Arkansas Code of 1987, state statutes by citation and by topic search. Fleet #2881, closing the… This page covers its npm package (@pipeworx/mcp-arkansas-code).

### Is the Arkansas Code MCP server safe to use?

Arkansas 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 Arkansas Code MCP server expose?

Arkansas Code exposes 2 tools: ar_statute, ar_search. Their descriptions and schemas cost roughly 514 tokens of context every time the server is loaded.

### Is the Arkansas Code MCP server still maintained?

Arkansas 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 Arkansas Code MCP server under?

Arkansas 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.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-arkansas-code
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-arkansas-code
- Repository: https://github.com/pipeworx-io/mcp-arkansas-code
- Website: https://pipeworx.io/packs/arkansas-code
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-arkansas-code/pipeworx-mcp-arkansas-code.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-arkansas-code/pipeworx-mcp-arkansas-code.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-arkansas-code/pipeworx-mcp-arkansas-code