Oregon Code
NPM · @PIPEWORX/MCP-OREGON-CODE · 2 COMPONENTS
Oregon Revised Statutes — state statutes by citation.
Available components
Last scanned (6 hours ago)
Scores higher than 65% 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-oregon-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 Usability71
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 174 tokens (~174/item across 1 items; 1 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 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
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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.
- 5 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- Security disclosure: unverified → fail ▼ functional
- 4 Nov 26 65
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-oregon-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-oregon-code |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-oregon-code/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3685190300 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:2536536f7b8deb5cf6bc693dc8c5a39af05a7efc845f79ee6053c4f6baf45afa2f2d06181772470bde5c31e252d1037e7f7e61c30c123dc5b64e41de8 |
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 →
or_revised_statute ~119
Get the FULL TEXT of a section of the Oregon Revised Statutes — Oregon state law — by citation. "ORS 163.115" is second degree murder. Returns the statutory text. Keyless. Use for "what does ORS 163.115 say" or to check an Oregon statute a case relies on.
| Name | Type | Req | Description |
|---|---|---|---|
| section | string | yes | Section as cited, e.g. "163.115" (murder 2) or "813.010" (DUII). Chapter is the part before the dot. |
No output schema declared.
No examples provided.
How do I install the Oregon Code MCP server?
Oregon Code runs locally as an npm package, launched with npx -y @pipeworx/mcp-oregon-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-oregon-code
claude mcp add pipeworx-io-oregon-code -- npx -y @pipeworx/mcp-oregon-code
What is the Oregon Code MCP server?
Oregon Code is an MCP server listed in the public MCP registry as io.github.pipeworx-io/oregon-code. Oregon Revised Statutes, state statutes by citation. This page covers its npm package (@pipeworx/mcp-oregon-code).
Is the Oregon Code MCP server safe to use?
Oregon Code scores 80 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 Oregon Code MCP server expose?
Oregon Code exposes 1 tool: or_revised_statute. Their descriptions and schemas cost roughly 119 tokens of context every time the server is loaded.
Is the Oregon Code MCP server still maintained?
Oregon 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 Oregon Code MCP server under?
Oregon 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.