Oklahoma Code
NPM · @PIPEWORX/MCP-OKLAHOMA-CODE · 2 COMPONENTS
Oklahoma Statutes — state statutes by citation, full-text topic search, amendment history, and…
Available components
Last scanned (12 hours ago)
Scores higher than 77% 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-oklahoma-code). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 1 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability69
- AI-judged instruction clarity (excellent).Pass
- 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. 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
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.
- 4 Nov 26 +16
- Malware scan: unverified → pass ▲ security
- 3 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- Package version: 0.2.0 → 0.2.1 functional
- 2 Nov 26 +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.
- 31 Oct 26 +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.
- 30 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 80
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-oklahoma-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-oklahoma-code |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-oklahoma-code/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3679677125 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:05404843502d7263b6797d940a0b2f420d6232b1268443fc5aedb5952fd35183fabd7a5a4d342d930f67cd8cb56edde03da52ad21c9a3dc3aca8b3c05 |
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 →
ok_search ~160
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max results to return, default 10, max 50. |
| query | string | yes | Topic or keywords, e.g. "landlord security deposit". |
No output schema declared.
No examples provided.
ok_statute ~311
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.
| Name | Type | Req | Description |
|---|---|---|---|
| citation | string | yes | 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… |
No output schema declared.
No examples provided.
ok_titles ~71
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
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.
npm · @pipeworx/mcp-oklahoma-code
claude mcp add pipeworx-io-oklahoma-code -- npx -y @pipeworx/mcp-oklahoma-code
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.