# Oklahoma Code (npm · @pipeworx/mcp-oklahoma-code)

Oklahoma Statutes — state statutes by citation, full-text topic search, amendment history, and…

- Trust score: 83/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`: 85/100, [markdown](https://verifymcp.io/servers/pipeworx-io-oklahoma-code/oklahoma-code-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-oklahoma-code/oklahoma-code-mcp)
- npm · `@pipeworx/mcp-oklahoma-code`: 83/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-oklahoma-code/pipeworx-mcp-oklahoma-code.md), [page](https://verifymcp.io/servers/pipeworx-io-oklahoma-code/pipeworx-mcp-oklahoma-code)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-oklahoma-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-oklahoma-code).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 1 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 597 tokens (~199/item across 3 items; 3 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 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 Oklahoma Code MCP server?

Oklahoma Code runs locally as an npm package, launched with npx -y @pipeworx/mcp-oklahoma-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-oklahoma-code -- npx -y @pipeworx/mcp-oklahoma-code
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-oklahoma-code": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-oklahoma-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-04 (score 83, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-11-03 (score 67, −15)

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

### 2026-11-02 (score 82, +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-10-31 (score 81, +1)

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

### 2026-10-30 (score 80, 0)

- [functional regression] Security disclosure: unverified → fail

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

First indexed and scored.

## MCP tools (3)

### `ok_statute` (~311 tokens)

Get the FULL TEXT of a section of the Oklahoma Statutes by citation, e.g. "21-701.7" (Murder in the First Degree) or "41-111" (termination of tenancy). Accepts "21-701.7", "21 O.S. 701.7", or "21 O.S. § 701.7". Returns the current statutory text, its chapter breadcrumb, the "Cite as" line, its full amendment history (every amending Act), and a historical_versions list of every prior (superseded) version with a citeid you can pass back as version_citeid to retrieve that EXACT prior text. Keyless. Use for "what does 21 O.S. 701.7 say", "Oklahoma murder statute", or to check an Oklahoma statute a case or contract relies on, including how it read before a given amendment.

Input parameters:

- `citation` (string, required): Section citation as title-section, e.g. "21-701.7" or "41-111". The title is the part before the dash/space and may carry a letter suffix (e.g. "10A-1" or "85A-45").
- `version_citeid` (number): Optional. A "citeid" value from a previous result's historical_versions array — fetches that superseded version's exact text instead of the current one. When set, "citation" is optional (used only to…

### `ok_search` (~160 tokens)

Search the Oklahoma Statutes by TOPIC or keyword rather than citation, e.g. "landlord", "concealed carry permit", "DUI per se limit". Real full-text search over statutory body text (not just captions) — a query like "landlord" surfaces sections whose heading never says "landlord" (e.g. "Termination of Tenancy", 41 O.S. § 111). Returns matching citations, headings, effective dates, and relevancy. Call ok_statute with a result's citation for the full text. Keyless.

Input parameters:

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

### `ok_titles` (~71 tokens)

List all 94 titles of the Oklahoma Statutes with their official names, e.g. Title 21 is Crimes and Punishments, Title 41 is Landlord and Tenant. Routing help for when you know the subject but not the title number — call this or ok_search before guessing a citation. Keyless.

## Diagnostics

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

## Score history

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

## Common questions

### What is the Oklahoma Code MCP server?

Oklahoma Code is an MCP server listed in the public MCP registry as io.github.pipeworx-io/oklahoma-code. Oklahoma Statutes, state statutes by citation, full-text topic search, amendment history, and… This page covers its npm package (@pipeworx/mcp-oklahoma-code).

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

Oklahoma Code scores 83 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 Oklahoma Code MCP server expose?

Oklahoma Code exposes 3 tools: ok_statute, ok_search, ok_titles. Their descriptions and schemas cost roughly 542 tokens of context every time the server is loaded.

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

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

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

VerifyMCP ran 16 checks on Oklahoma 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.

## Links

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