
Virgin Islands Code MCP server
online · 100% uptimeVirgin Islands Code (V.I.C.) — US Virgin Islands statutes, 2026 edition: full section text by…
not scanned yet
0 stars
Reviews
Write oneNobody has reviewed Virgin Islands Code yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Virgin Islands Code tools
Tool list not cached yet. `describe` through the gateway fetches it live.
How Virgin Islands Code compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 77/100
- higher than 50% of 48,255 servers
- Uptime
- 100%
- of our recent checks; the typical remote server answers 100%
- Response time
- 190 ms
- faster than 65% of 30,031 servers
Release history: 2 versions in the registry since 2026-10-13, latest 2026-10-29, typically one every 16 days.
Install Virgin Islands Code in Claude Code, Cursor or VS Code
claude mcp add --transport http virgin-islands-code https://gateway.pipeworx.io/virgin-islands-code/mcp
What the publisher says
From the Virgin Islands Code repository's README, as published. We do not edit it. Read it on GitHub
@pipeworx/virgin-islands-code
Virgin Islands Code (V.I.C.), the statutes of the US Virgin Islands, 2026 edition — full section text by citation, keyword search within a title, and the list of all 37 titles. Keyless.
Part of Pipeworx — an MCP gateway connecting AI agents to 1773+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.
Tools
("14 V.I.C. § 922" is first and second degree murder; "11A V.I.C. § 2-201" is the UCC statute of frauds). Also accepts "14 VIC 922", "V.I. Code Ann. tit. 14, § 922" and "Title 14, Section 922". Returns the heading, the statutory text and the "History:" amendment line.
- vi_statute(citation) — full text of a V.I.C. section by citation
word must appear in a section's heading or text. Heading matches list first, then code order. Returns citations, headings and a snippet.
- vi_search(title, query, limit?) — keyword search inside ONE title; every
names and section counts, for routing a subject to a title.
- vi_titles() — all 37 titles (1-34 plus 11A, 12A, 15A) with their official
A miss is an answer, not an error: an unknown title, a section the title does not carry, or a search with no match returns found: false with a reason and dataasof. An upstream failure (non-404 status, timeout, a page that no longer has the section markup) is a loud error, never found: false.
Auth
Keyless.
Data sources
Islands Code 2026 edition — the archive's own text edition, set from the Virgin Islands Code 2026 Edition, all 37 titles and 12,420 sections.
- USVI Public Records (a VI Update project, usvipublicrecords.com), Virgin
Why this source
The Virgin Islands was the one US jurisdiction without a code pack after DC and the other four inhabited territories shipped (fleet #2888-#2892). The only free copy of the current Code we had found sat behind a bot check, and the commercial publisher bars automated access (fleet #2907). Bruce pointed at USVI Public Records, which publishes the Code as readable text.
Reuse terms
From the publisher's own pages, quoted:
statutory text is an edict of government and belongs to no one."*
- The Code page: *"This is the archive's own edition of a public text; the
"U.S. government works (public domain), acts and edicts of the V.I. government (uncopyrightable by law) …"
- USVI Public Records' terms page, on what the archive itself carries:
for a person are all welcome"*, with Content-Signal: search=yes, ai-input=yes, ai-train=yes.
- Its robots policy: *"Search engines, AI answer engines and assistants acting
This pack fetches per request and copies nothing in bulk.
Being a polite client
The publisher bills the website host per gigabyte and asks software not to crawl it. The Code is only published there, one page per title (Title 14 is ~770 KB, Title 11A ~1.1 MB), so:
repeated lookups in the same title cost the publisher about one request a day;
- every fetch asks Cloudflare to keep the title page at the edge for a day, so
every query.
- vi_search needs a title instead of fanning out across all 37 pages for
If traffic grows enough that a full copy makes sense, ask the publisher first (tips@viupdate.com is on their machine-access page). Don't start crawling.
Edge probe
Checked 2026-10-12 from a throwaway elias-vi-probe Worker running under wrangler dev --remote, sending this pack's User-Agent:
There's no challenge page and no block on Worker egress.
Page shape, for whoever touches the parser
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Virgin Islands Code: common questions
- Is Virgin Islands Code MCP server safe?
- Mostly: it is graded B (77/100). Read the Virgin Islands Code safety report
- How do I install Virgin Islands 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 Virgin Islands Code need an API key?
- Yes. The registry entry asks for
PIPEWORX_API_KEY. - Is Virgin Islands Code maintained?
- The last commit was 22 days ago (2026-10-13). The latest release is v0.2.0.
- Is Virgin Islands Code up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.
- How does Virgin Islands Code compare with other MCP servers?
- safety score 77/100 (higher than 50% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 190 ms (faster than 65% of 30,031 servers). Full comparison.