
Wyoming Code MCP server
online · 100% uptimeWyoming Statutes (W.S.) — state statutes by citation and by topic. Fleet #2744.
not scanned yet
0 stars
Reviews
Write oneNobody has reviewed Wyoming Code yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Wyoming Code tools
Tool list not cached yet. `describe` through the gateway fetches it live.
How Wyoming Code compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 73/100
- higher than 39% of 48,255 servers
- Uptime
- 100%
- of our recent checks; the typical remote server answers 100%
- Response time
- 280 ms
- faster than 50% of 30,031 servers
Release history: 5 versions in the registry since 2026-10-10, latest 2026-10-29, typically one every 4 days.
Install Wyoming Code in Claude Code, Cursor or VS Code
claude mcp add --transport http wyoming-code https://gateway.pipeworx.io/wyoming-code/mcp
What the publisher says
From the Wyoming Code repository's README, as published. We do not edit it. Read it on GitHub
Wyoming Statutes (W.S.)
Wyoming Statutes by citation, plus full-text topic search. Keyless.
Part of Pipeworx — an MCP gateway connecting AI agents to 1765+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.
Source (fleet #2744)
The Wyoming Legislative Service Office (wyoleg.gov) runs an Angular SPA for its "Wyoming Statutes & Constitution" page. Probed live 2026-10-06 by downloading the SPA's own JS bundles (main-.js, the lazily-loaded chunk-lXRwsur.js for its StateStatutesModule) and grepping for an API base URL or any lsoservice.wyoleg.gov reference — none exists for statute TEXT. The "Download the Wyoming Statutes" page is a plain static list of links to per-TITLE PDFs:
https://wyoleg.gov/statutes/compress/title06.pdf (Title 6, Crimes and Offenses)A .docx sibling (the task's other named possibility) does NOT exist — every .docx path probed (several casings and locations) returns the SPA's own catch-all shell (HTTP 200, not a real 404), confirmed by checking content-type/length rather than status code. PDF is the only route.
The PDF trap, and why shared/src/pdf-text.ts needed extending
Wyoming's per-title PDFs are PDF 1.6, linearized, and store their Catalog and Pages root inside a compressed object stream (/Type/ObjStm) — a shape shared/src/pdf-text.ts explicitly did not support before this pack (its own header said so; Kentucky's PDFs, the only prior user, never hit it). Verified directly against Title 6's PDF: 5205 0 obj (its Pages root) never appears literally in the file at all; it exists only as an entry inside a decompressed ObjStm. Separately, the Catalog object IS direct but the original discovery regex broke the moment a nested dict (/MarkInfo<>) appeared before /Type/Catalog in the same object — also true here, not Wyoming- specific bad luck.
Both gaps are now fixed in shared/src/pdf-text.ts itself (see that file's header for the mechanism), not worked around in this pack, since a future PDF-only state with a compressing producer hits the identical wall. Verified end-to-end: Title 6 (441 KB, 210 pages) extracts to 387,932 characters with zero warnings, and W.S. 6-2-101 ("Murder in the first degree") comes back with its correct text.
MB-scale files — never fetched whole per call
Per-title PDFs run from ~300 KB (Title 97, the Constitution — not covered, see below) to ~2.9 MB (Title 35, Public Health and Safety) across the 44 titles this pack covers. Exactly like mcps/indiana-code, one JSON bundle per title is pre-fetched into the shared pipeworx-datasets R2 bucket (statutes/wy/.json, via scripts/ingest-wyoming-statutes.mjs) plus a full-text search shard (wy-statutes). wy_statute reads the pre-sliced section straight out of the bundle; a live PDF fetch is the FALLBACK only — for a title the bundle does not yet cover, or a standalone (non-hosted) install with no R2 binding — and even then fetches only the ONE requested title's PDF, never the whole corpus.
Tools
citation ("6-2-101" is murder in the first degree, Title 6; "20-1-105" is divorce grounds, Title 20). Accepts "6-2-101", "W.S. 6-2-101", "§ 6-2-101". Returns the current text, the section heading, and — only where the source carries one cleanly — an enactment history note (see below).
- wy_statute(citation) — full text of a Wyoming Statutes section by
across all 44 covered titles via the shared FTS5 search shard. Returns matching citations and headings; call wy_statute for the full text.
- wy_search(query, limit?) — full-text search over the statutory body text
Citations
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Wyoming Code: common questions
- Is Wyoming Code MCP server safe?
- Mostly: it is graded B (73/100). Read the Wyoming Code safety report
- How do I install Wyoming Code?
- It runs remotely at gateway.pipeworx.io. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does Wyoming Code need an API key?
- Yes. The registry entry asks for
PIPEWORX_API_KEY. - Is Wyoming Code maintained?
- The last commit was 24 days ago (2026-10-10). The latest release is v0.2.0.
- Is Wyoming Code up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.
- What can I use instead of Wyoming Code?
- Servers from other publishers that do the same job: Korean Law MCP server.
- How does Wyoming Code compare with other MCP servers?
- safety score 73/100 (higher than 39% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 280 ms (faster than 50% of 30,031 servers). Full comparison.
Alternatives to Wyoming Code
Same job from other publishers: the closest match first, then the best rated.
- Korean Law MCPKorean law: statutes, precedents, ordinances, treaties and citation verification (법제처 API).not reviewedEstablishedA