Alaska Code MCP server

@pipeworx/alaska-code

Alaska Statutes (Alaska Code) — current statutory text by citation, and topic/keyword search over official chapter catchlines, sourced live from www.akleg.gov.

Part of Pipeworx — an MCP gateway connecting AI agents to 1715+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.

Tools

"4.11.010" / "AS 04.11.010", alcohol-license requirements; "11.41.100", murder), with the official catchline and title/chapter context.

• ak_statute({citation}) — full text of one section by citation (e.g.

chapter catchlines across all 47 titles, e.g. "alcohol license", "murder". Not full-text search, and not section-level — akleg.gov exposes neither keylessly (see "Data sources").

• ak_search({query, limit?}) — topic/keyword search over the 942 live

Auth

Keyless. No signup, no activation gate.

Data sources

https://www.akleg.gov/basis/statutes.asp — the Alaska State Legislature's own public statute viewer. It is driven as a GET AJAX endpoint (the page's own scripts/statutes.js calls it this way):

the half-open citation range [secStart, secEnd). Citation shape is title.chapter.section, e.g. 4.11.010. ak_statute always requests a single section (secEnd = the next section number) and gets back exactly one statute div block with no preceding Article/Chapter heading markup.

• ?media=print&secStart={citation}&secEnd={citation} — statute text for

catchline) for Title N. Baked once into src/ak-index-data.ts by scripts/bake-index.mjs (47 requests, one per title).

• ?media=js&type=TOC&title={N} — the chapter list (number + official

Verified live from both a laptop and a wrangler dev --remote Worker on the prod account on 2026-10-07 — identical byte lengths from both origins. Keyless, access-control-allow-origin: *.

The "not found" signal

A secStart/secEnd range that matches nothing — a nonexistent title, a nonexistent chapter, or a genuine gap number inside a real chapter — always comes back HTTP 200 with a zero-length body and no FirstSec/LastSec response headers (all three cases verified live). A real section returns a non-empty body. ak_statute branches on body length, not status code — a non-200 status, or a non-empty body that does not parse as a statute fragment, is thrown loud (httpError / a parse-error Error), never folded into found: false.

Not the same wall as Arkansas or Mississippi

Both of those states' own legislature sites link their code out to lexisnexis.com/hottopics/code/, which redirects to an advance.lexis.com/container?config=... SPA shell requiring a Lexis session — confirmed live and at the edge (same destination host, same 3,696-byte shell, for both states). Alaska's own site serves the statute text itself, server-side, with no redirect to any third-party platform.

Two capabilities available, two not

(942 of them). akleg.gov's type=TOC call returns "No Sections" for a dotted (title.chapter) argument rather than a per-section listing (verified live) — unlike Idaho, there is no section-level catchline feed to bake.

• Citation lookup — ak_statute.
• Topic/keyword search — ak_search, over official CHAPTER catchlines only

this endpoint returns carries no trailing history citation (checked against AS 11.41.100, a frequently amended section with multiple [Repealed, ...] sub-paragraphs and nothing after them).

• Amendment history — NOT AVAILABLE. Unlike Idaho, the statute fragment

AVAILABLE**, for the same reason as idaho-code and north-dakota-code: Session Laws are organized by session chapter number, not by Code citation.

• Historical version (text as it read before an amendment) — **NOT

Encoding

Shortened. The full README is on GitHub.