Colorado Code
NPM · @PIPEWORX/MCP-COLORADO-CODE · 2 COMPONENTS
Colorado Revised Statutes — state statutes by citation, topic, and title.
Available components
Last scanned (23 hours ago)
Scores higher than 72% 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-colorado-code). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 3 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability68
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
- Stability observed for 6 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
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.
- 3 Nov 26 +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.
- 1 Nov 26 +26
- Known CVEs: unverified → pass ▲ security
- Malware scan: unverified → pass ▲ security
- Dependency health: unverified → pass ▲ functional
- 31 Oct 26 −25
- Known CVEs: pass → unverified ▼ security
- Malware scan: pass → unverified ▼ security
- Dependency health: pass → unverified ▼ functional
- Stability: unverified → 0.07 ▲ functional
- Package version: 0.2.0 → 0.2.1 functional
- 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 4 Nov 2026 · Analysed npm/@pipeworx/mcp-colorado-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-colorado-code |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-colorado-code/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3612183373 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:a6c03c87d935bfb5eae781d3fe1bc8d34845c336205f83260393f5e5dd1852038de996c9ed108cd42fd5095564cfeab1cda5cf0d8086a27c67691b425 |
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 →
co_search ~209
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max results to return (default 15, max 50). |
| query | string | yes | Topic to search for, e.g. "landlord", "security deposit", "concealed handgun". Short phrases work best. |
No output schema declared.
No examples provided.
co_statute ~248
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.
| Name | Type | Req | Description |
|---|---|---|---|
| section | string | yes | 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. |
No output schema declared.
No examples provided.
co_titles ~101
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.
| Name | Type | Req | Description |
|---|---|---|---|
| subject | string | – | Optional subject to filter by, e.g. "divorce", "DUI", "landlord". |
No output schema declared.
No examples provided.
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.
npm · @pipeworx/mcp-colorado-code
claude mcp add pipeworx-io-colorado-code -- npx -y @pipeworx/mcp-colorado-code
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 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 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 4 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.