# Colorado Code (npm · @pipeworx/mcp-colorado-code)

Colorado Revised Statutes — state statutes by citation, topic, and title.

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

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-colorado-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-colorado-code).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 4 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 68/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 611 tokens (~203/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 Colorado Code MCP server?

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

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

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

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

### 2026-11-03 (score 82, +1)

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

### 2026-11-01 (score 81, +26)

- [security improvement] Known CVEs: unverified → pass
- [security improvement] Malware scan: unverified → pass
- [functional improvement] Dependency health: unverified → pass

### 2026-10-31 (score 55, −25)

- [security regression] Known CVEs: pass → unverified
- [security regression] Malware scan: pass → unverified
- [functional regression] Dependency health: pass → unverified
- [functional improvement] Stability: unverified → 0.07
- [functional] Package version: 0.2.0 → 0.2.1

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

- [functional regression] Security disclosure: unverified → fail

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

First indexed and scored.

## MCP tools (3)

### `co_statute` (~248 tokens)

Get the FULL TEXT of a section of the Colorado Revised Statutes (C.R.S.) — Colorado state law — by citation. "C.R.S. 18-3-102" is murder in the first degree. Returns the statutory text, the amendment "Source:" history, and cross references. Pass "year" (2000-current, except 2025 which is not yet supported) to get an older edition instead of the current one, e.g. to see how a section read before a given amendment. Keyless. Use for "what does C.R.S. 18-3-102 say", "Colorado landlord security deposit law", or to check a Colorado statute a case relies on.

Input parameters:

- `section` (string, required): Section as cited, e.g. "18-3-102" (murder) or "38-12-103" (security deposits). Title-article-section; the title is the part before the first dash.
- `year` (integer): Optional. A C.R.S. edition year from 2000 through the current year, to retrieve a historical version of the section instead of the current one. Omit for the current edition.

### `co_titles` (~101 tokens)

List the 44 titles of the Colorado Revised Statutes with their official names — Title 18 is the Criminal Code, Title 42 is Vehicles and Traffic, Title 38 is Property, and so on. Keyless. Use when you know the subject but not the title number, before calling co_statute or co_search.

Input parameters:

- `subject` (string): Optional subject to filter by, e.g. "divorce", "DUI", "landlord".

### `co_search` (~209 tokens)

Search the Colorado Revised Statutes GENERAL INDEX by topic and get back matching index entries with their C.R.S. citations — e.g. "landlord", "security deposit", "concealed handgun", "driving under the influence". This is a real subject-index search, not just a title list: it finds the specific section(s) a plain-English topic maps to so you can pass them to co_statute. Works best with a SHORT topic (1-3 words) — the index is a nested tree (a topic heading followed by indented sub-entries that do not repeat the heading word), matched here within a small window of nearby lines, so a long compound phrase can miss or pick up a loosely related neighbor. Keyless.

Input parameters:

- `limit` (integer): Max results to return (default 15, max 50).
- `query` (string, required): Topic to search for, e.g. "landlord", "security deposit", "concealed handgun". Short phrases work best.

## Diagnostics

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

## Score history

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

## Common questions

### What is the Colorado Code MCP server?

Colorado Code is an MCP server listed in the public MCP registry as io.github.pipeworx-io/colorado-code. Colorado Revised Statutes, state statutes by citation, topic, and title. This page covers its npm package (@pipeworx/mcp-colorado-code).

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

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

Colorado Code exposes 3 tools: co_statute, co_titles, co_search. Their descriptions and schemas cost roughly 558 tokens of context every time the server is loaded.

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

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

Colorado 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-colorado-code
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-colorado-code
- Repository: https://github.com/pipeworx-io/mcp-colorado-code
- Website: https://pipeworx.io/packs/colorado-code
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-colorado-code/pipeworx-mcp-colorado-code.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-colorado-code/pipeworx-mcp-colorado-code.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-colorado-code/pipeworx-mcp-colorado-code