@pipeworx/colorado-code

Connect: https://pipeworx.io/mcp — every tool in the catalog, including @pipeworx/colorado-code’s. Install: one-click buttons

No MCP client? Skip the connection: POST https://gateway.pipeworx.io/v1/tools/search_packs {"query":"..."} to find a tool below, GET /v1/tools/<name> for its schema, POST the same URL with arguments for the data — see For AI agents.

Tools: 5

Keyless. “C.R.S. 18-3-102” returns murder in the first degree.

The official site redirects into a wall; a second official route does not

leg.colorado.gov’s “C.R.S. Online” link does not host the text itself — it redirects into advance.lexis.com, a JS-rendered, cookie-session SPA whose own next step is a login-capture redirect (CaptureReturnUrl). That is the same class of wall this pack family declines (ASP.NET postback / anti-bot), and it has no stable per-citation URL to probe anyway.

The Office of Legislative Legal Services separately publishes the whole C.R.S. as downloadable files, one per title, on its own plain file server — no login, no JS, keyless:

https://olls.info/crs/crs2026-title-18.htm         (current edition)
https://olls.info/crs-archive/CRS-2015-TITLE-18.htm (a historical edition)

Files are per title, citations are per section — and titles are BIG

A title file holds the whole title plus case-law annotations after every section (Title 18 alone is ~9.5MB), so the section is cut out of it bounded by the next section heading OR the start of the annotations, whichever comes first. Annotations are Lexis’s editorial case-law commentary, not the statute, and are never returned — only the statutory text, the Source: amendment history, and Cross references: (all public law).

The cut runs on the raw HTML, not the tag-stripped text, on purpose: a real section heading is the only place a citation is wrapped in <b><span>NUM.</span></b>. The per-article mini table-of-contents that precedes every article, and plain cross-references inside OTHER sections’ annotations (a citation that happens to land at the start of a text line once tags are stripped), both repeat the same number unbolded — textually indistinguishable from a heading after stripping, never bold in the source.

Three file formats across 27 years of archive

Checked against Title 18 (old enough to exist in every edition):

2025 is declined explicitly (edition_format_unsupported) rather than risk a silently wrong parse for one edition out of twenty-seven — almost certainly a one-year migration artifact between the other two generators. If a future year changes format again, co_statute will start answering section_not_found for a title that exists; the same risk every sibling state pack already takes on the current year alone, just extended here across 25 archived years too.

Topic search is a nearby-heading window, not full hierarchy awareness

co_search runs against the ~18MB General Index (crs2026-index.htm), which is a nested tree — a topic heading followed by indented sub-entries that do not repeat the heading word. Matching only a result line misses that structure, so each query word is matched within a small window of the lines immediately preceding a citation-bearing entry. This works well for short topics (1-3 words: “landlord”, “security deposit”, “concealed handgun”) and gets noisier on long compound phrases, which is why the tool description says so.

The four capabilities

• By citation — co_statute. Yes.
• By topic — co_search (General Index) and co_titles (title list with subject hints). Yes, with the window caveat above.
• Historical version — co_statute with year, 2000-2024 and current; 2025 declined (see above). Yes, mostly.
• Amendments/history — the Source: line, surfaced as history. Yes for the current template and 2000-2024; for 2000-2024 editions cross_references is usually null because that era files “Cross references:” inside the annotations block this pack deliberately excludes.

Data sources

• https://olls.info/crs/ — current C.R.S. edition, by title.
• https://olls.info/crs-archive/ — archived editions back to 2000, by title and year. robots.txt disallows crawling this path for SEO; that is not a redistribution question for data this public (CLAUDE.md’s standing ruling).
• https://olls.info/crs/crs2026-index.htm — the General Index, for co_search.

Colorado Office of Legislative Legal Services. Colorado statutes are public record.

Regulations (Code of Colorado Regulations)

Statutes are the law the legislature passed; regulations are the rules the agencies make under it. co_regulation and co_regulation_search cover the Code of Colorado Regulations (CCR), published by the Colorado Secretary of State. Every call goes to the publisher live; nothing is stored.

• co_regulation(ccr_number, rule?, effective_date?, offset?, max_chars?) — "1 CCR 212-3" is the Colorado Marijuana Rules. With rule: "2-245" it returns that one rule (change of controlling beneficial owner, i.e. transfer of ownership) with the document’s effective date; without rule it pages through the document and lists its rule numbers. It also returns the filing type, adopted date, Colorado Register publication, eDocket tracking number and every earlier effective date (pass effective_date for one of them). A citation naming only an agency ("2 CCR 502") returns that agency’s document list.
• co_regulation_search(query, department?, page?) — keyword search over the rule documents, returning CCR number, title, department, agency and effective date. It finds documents, not single rules.

The publisher’s official version of each rule document is a PDF. Text is read out of it, so tables and layout are flattened; the page headers are removed and rule headings are used to cut one rule out of its document. Where a document numbers its rules differently from the Marijuana Rules, rule may report rule_not_found; page through the text with offset instead.

Source: Colorado Secretary of State, Code of Colorado Regulations. Colorado regulations are public record.

Tools

• co_statute — 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
• co_titles — 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
• co_search — 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 t
• co_regulation — Get the TEXT of a Colorado administrative regulation (Code of Colorado Regulations, CCR) by citation, with its effective date. “1 CCR 212-3” is the Colorado Marijuana Rules; pass rule=“2-245” to read
• co_regulation_search — Search the Code of Colorado Regulations (Colorado state administrative rules) by keyword and get back the matching rule DOCUMENTS with CCR number, title, department, agency and effective date — e.g.