South Dakota Code MCP server

@pipeworx/south-dakota-code

South Dakota Codified Laws (South Dakota state statutes) — full section text by citation, and topic/keyword search over official catchlines.

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

Tools

"22-16-4", murder in the first degree), with the official catchline, chapter/title context, and — when the section carries one — the "Source:" line listing every session law that enacted or amended it, split out into history.

• sd_statute(citation) — full current text of one SDCL section (e.g.

own official section and chapter catchlines across all 71 titles (e.g. "landlord", "concealed pistol permit"). Not full-text search — South Dakota does not publish one.

• sd_search(query, limit?) — topic/keyword search over the Legislature's

Auth

Keyless.

Data sources

(or chapter's, or title's) current text, as JSON with an Html field. sd_statute calls this live, per request, for a section-shaped citation.

• https://sdlegislature.gov/api/Statutes/Statute/{citation} — one section's

Used only by scripts/bake-index.mjs to drive the per-title fetch below.

• https://sdlegislature.gov/api/Statutes/Title — the list of all 71 titles.

Capabilities — three available, one is not

South Dakota's own publication covers:

section's text ends with a "Source: SDC 1939, § 13.2007 (1); SL 1979, ch 160, § 2; ..." line listing every session law that created or amended it (verified live on 22-16-4). sdstatute splits this into history rather than leaving it only embedded in text. A repealed/transferred section's one-line disposition (e.g. "22-16-9. Repealed by SL 2005, ch 120, § 158, eff. July 1, 2006.") comes back as dispositiontext, with repealed: true read from the API's own flag.

• Citation lookup — sd_statute.
• Topic/keyword search — sd_search, over catchlines only (see below).
• Amendments/enactment history — PARTIALLY AVAILABLE. An in-force

AVAILABLE. sdlegislature.gov publishes only the CURRENT online edition: no per-year archive, no "view as of" date picker, and no endpoint returning a prior version's text (checked the site's own JS bundle for one — none exists). The Source: line says WHEN and by WHICH session law a section was amended; it does not return what the text read before that.

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

Source and shape — read this before touching the parser

sdlegislature.gov is a Vue single-page app. The August state-law survey (docs/state-law-probe.md) correctly flagged the HTML shell as carrying no statute — it just stopped one layer too early. The SPA itself is fed by a keyless, public JSON API under /api/Statutes/ (found by grepping the site's own JS bundle for /api/Statutes — no documentation page exists for it): GET /api/Statutes/Statute/{citation} accepts a section citation ("22-16-4"), a chapter citation ("22-16") or a title number ("22"), and returns one JSON envelope whose Html field is that level's content — full section text for a section, or a plain table-of-contents listing (chapter header + every section's citation and catchline, with NO body text) for a chapter or title. No auth, no key, no rate limit observed.

sd_statute only ever calls the section-shaped form, live, per request — never baked.

sd_search needs a structural index (every citation + its official catchline) to search over, and there is no search endpoint and no single "whole code" listing page the way North Dakota publishes one. The only way to assemble one is to call the TITLE-level form for each of the 71 titles and parse its table-of-contents Html blob. scripts/bake-index.mjs does this once, offline, into src/sd-index-data.ts — never at request time.

Shortened. The full README is on GitHub.