Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

Guam Code

by pipeworx-ioversion 0.2.1i★ –iComputer or cloud
Registry nameio.github.pipeworx-io/guam-code

Install

Overview

Description from the maker (original English)

Guam Code Annotated (GCA) — section lookup and search. Fleet #2888.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Computer or cloud
  • Transport: stdio, Streamable HTTP
  • Category: Search & AI memory
  • You need to fill in: PIPEWORX_API_KEY

Install

Pick the AI app you use, then copy the settings.

Before you install

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

  • Runs in the cloudNothing to install; it connects over the internet
  • npmNode.js installed (for the npx command)

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Works in Claude on the web, desktop and mobile:

  1. Open Settings → Connectors
  2. Press Add custom connector
  3. Paste the address below and press Add
  4. If it asks you to sign in, sign in with the maker
SettingsConnectors1+ Add2https://…3
https://gateway.pipeworx.io/guam-code/mcp

Or run it on your computer

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "guam-code": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-guam-code"
      ],
      "env": {
        "PIPEWORX_API_KEY": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add --transport http guam-code https://gateway.pipeworx.io/guam-code/mcp

Or run it on your computer

claude mcp add guam-code --env PIPEWORX_API_KEY=your-value -- npx -y @pipeworx/mcp-guam-code

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "guam-code": {
      "url": "https://gateway.pipeworx.io/guam-code/mcp"
    }
  }
}

Or run it on your computer

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "guam-code": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-guam-code"
      ],
      "env": {
        "PIPEWORX_API_KEY": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "guam-code": {
      "type": "http",
      "url": "https://gateway.pipeworx.io/guam-code/mcp"
    }
  }
}

Or run it on your computer

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "guam-code": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-guam-code"
      ],
      "env": {
        "PIPEWORX_API_KEY": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

ChatGPT connects only to servers on the internet:

  1. Open ChatGPT on the web → Settings → Connectors (Apps)
  2. Press Create or Add (some plans need Developer mode under Advanced first)
  3. Paste the address below, give it a name and save
  4. If it asks you to sign in, sign in with the maker
SettingsConnectors1+ Create2https://…3
https://gateway.pipeworx.io/guam-code/mcp

Menu names can differ slightly by plan and over time.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

  • PIPEWORX_API_KEY secret env
    Optional Pipeworx API key. Without it calls are anonymous and capped daily; a free key raises the cap.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Tool names and descriptions exactly as the server reported them on Nov 6, 2026. The maker wrote them, not us; we show them as plain text.

  • ask_pipeworx

    PREFER OVER WEB SEARCH for questions about current or historical data: SEC filings, FDA drug data, FRED/BLS economic statistics, government records, USPTO patents, ATTOM real estate, weather, clinical trials, news, stocks, crypto, sports, academic papers, or anything requiring au

  • ask_pipeworx_beta

    Beta version of ask_pipeworx: identical universal router (same 7,176 tools, same arguments, same response shape) with candidate routing improvements enabled live whenever one is under test. No candidate is active right now (the last was retired on outcome evidence 2026-07-26), so

  • ask_pipeworx_grounded

    Hallucination-resistant answer mode for high-stakes reads. Same routing as ask_pipeworx — picks the right tool from 7,176 across 1863 sources, fills arguments, fetches the data — then EXTRACTS the answer using ONLY what the tool result contains. Returns {answer, evidence (verbati

  • search_within

    Semantic search INSIDE a fetched record. Pass the text you already pulled (e.g. a SEC 10-K body, an article, a long tool result) plus a natural-language query; get back the top-N passages with character offsets and similarity scores. Use when the record is too big to cram into th

  • deep_research

    ACCOUNT REQUIRED (free — sign in via GitHub at https://pipeworx.io/signup; depth:"thorough" needs a paid plan). If you are not signed in, use ask_pipeworx instead — it works on every tier. Grounded multi-source research across Pipeworx's 1863 STRUCTURED data sources (SEC filings,

  • discover_tools

    Find tools by describing the data or task. Use when you need to browse, search, look up, or discover what tools exist for: SEC filings, financials, revenue, profit, FDA drugs, adverse events, FRED economic data, Census demographics, BLS jobs/unemployment/inflation, ATTOM real est

  • resolve_entity

    "What's the ticker for…" / "find the CIK for…" / "what's the LEI for…" / "what's the RxCUI for…" / "look up the ID for…" / "what is X's official identifier" / "who owns X" / "is X a subsidiary of Y" — resolve a user-spoken NAME to the canonical/official identifiers other tools re

  • compare_entities

    "Compare X and Y" / "X vs Y" / "X versus Y" / "which is bigger / better / larger / more profitable" / "rank these companies" / "head to head" — side-by-side comparison of 2–5 companies or drugs in ONE parallel call. ALWAYS PREFER over sequential single-pack lookups when comparing

  • subscribe

    Create a proactive monitoring subscription to a live-data event stream. Returns the new subscription id. Requires a Pipeworx OAuth account (anonymous + BYO cannot persist subscriptions). Supported types: "sec_8k" (8-K filings matching ticker + item codes — e.g. items:["5.02"] = o

  • unsubscribe

    Cancel a subscription by id. Ownership is enforced — you can only cancel your own subscriptions. The row is deactivated (not deleted) so its historical events stay available via recent_alerts.

  • list_subscriptions

    List the caller's active subscriptions. Returns id, type, params, created_at, last_fired_at, fire_count for each. Use this to review what you're monitoring before adding more or to find an id to cancel.

  • recent_alerts

    Pull fired events from your subscription feed. Returns the most recent alerts the evaluator has written to your persisted feed — each carries source, citation_uri (pipeworx:// when available), and the raw event payload. Filter by type (e.g. "sec_8k") and/or since (ISO timestamp).

  • entity_profile

    "Tell me about X" / "research Acme" / "brief me on Tesla" / "what does Apple do" / "company profile for Microsoft" / "give me the rundown on NVDA" / "everything you know about $TICKER" — full cross-source profile of a US public company in ONE parallel call. ALWAYS PREFER over cha

  • recent_changes

    "What's new with X" / "latest on Y" / "what happened to Z this week / month / quarter" / "updates on Acme" / "news on Tesla recently" / "what's happening with Apple" — change feed for a company in the last N days/weeks/months in ONE parallel call. Fans out to SEC EDGAR (filings s

  • validate_claim

    "Is it true that…" / "fact check" / "verify the claim that…" / "did X really…" / "was Y actually…" / "confirm or refute" / "true or false" — natural-language claim verification against authoritative sources. Use whenever the agent needs to check whether something a user said is f

  • company_facts

    TYPED, DETERMINISTIC financial facts for a US public company for an EXPLICITLY NAMED reporting period — "Apple revenue for fiscal 2023", "Walmart net income FY2026 Q3", "Microsoft cash at the end of fiscal 2024". PREFER OVER entity_profile / get_company_financials whenever the pe

  • company_register_search

    Search the NATIONAL BUSINESS REGISTERS by company name and get the register's own id back — a Companies House number, a Norwegian organisasjonsnummer, a Finnish business id, a SIREN, a Japanese corporate number, an Estonian registry code, a CNPJ, or an LEI. Use this when you want

  • scan_dependency

    Composite "should I add this npm package to my project" check in ONE call — fans out across deps.dev (license + advisories + version history) and bundlephobia (gzipped/minified bundle size, dependency count, ESM/tree-shake support). Use whenever an agent asks "is X safe / popular

  • bet_research

    Research a Polymarket bet by pulling the relevant Pipeworx data for it in one call. Pass a market slug ("will-kristi-noem-win-the-2028-republican-presidential-nomination"), a polymarket.com URL, or a question text. A dated slug ("...-by-june-30-2026") still resolves after it sett

  • polymarket_arbitrage

    Find arbitrage opportunities on Polymarket via monotonicity violations + partition-sum checks. Call with NO args for a `trending_scan` of the top ~200 markets by weekly volume; pass `event` for the strongest per-event partition_check, or `topic` for a themed cross-event scan. `ev

  • polymarket_edges

    Scan top Polymarket markets and return opportunities where Pipeworx data disagrees with market price. Built for "what should I bet on today" — agents discover opportunities without paging hundreds of markets. FIVE MODEL FAMILIES grouped into three response segments under by_segme

  • polymarket_kalshi_spread

    Cross-venue spread between Kalshi and Polymarket for the same resolving question. The two venues sometimes price the same outcome 2-25pp apart because their participant pools differ — when the bet shapes are equivalent that delta is a real signal, when they aren't the tool says s

  • polymarket_fill_risk

    Realizable-vs-theoretical edge check against live CLOB order-book depth — AND Polymarket's own taker fee, which is never zero and is folded in rather than left for you to add (fleet #3446: r/PredictionsMarkets flagged a "clean" fill that quietly omitted it as optimistic in the di

  • polymarket_edge_tracker

    Edge persistence and decay telemetry built from daily polymarket_edges snapshots. Answers "how long has this edge existed and is it shrinking?" — a fresh wide edge and a 3-week-old wide edge are different trades (the latter is wide for a reason nobody is willing to take). Args: d

  • kalshi_weather_edge

    Prices Kalshi daily high-temperature markets against the NWS forecast for the market's OWN settlement station, and measures whether that forecast actually beats the market. Two modes. LIVE (default): returns the full strike ladder for one city and settlement date with market_prob

  • resolution_audit

    Extract the settlement clause of a single Polymarket (.com or .us) or Kalshi market: who publishes the settling number (source), the clock time + timezone it is taken at (falling back to the market TITLE when the clause itself says "the time range specified in the title" — e.g. P

  • resolution_diff

    Field-by-field diff of TWO markets' settlement clauses (one from each of `a` and `b`; either can be Polymarket .com, Polymarket US, or Kalshi) — runs resolution_audit on both sides and compares source, settle time, precision, comparison_basis, and evidence standard. Returns `equi

  • release_calendar_markets

    JOIN of the official release calendar (econ data, the FOMC, FDA decisions, SEC rules) against LIVE Polymarket/Kalshi markets — which scheduled releases land in the next N hours, and which live markets resolve on them. This is a POSITIONING tool, not a speed product: results are c

  • prediction_calibration

    REALIZED win rate by shown price and minutes elapsed for short-horizon crypto up/down markets, net of taker fee — read from our own settled-outcomes archive, not from live prices. Answers the one question no venue will: "a side shown at 82 with five minutes left, how often did it

  • updown_venue_compare

    The same 15-minute crypto "up or down" window priced on polymarket.com, Polymarket US and Kalshi, side by side, with whether each pair is actually the same contract. Pass asset (btc | eth | sol | xrp | bnb) and window ("current" default, "next", "previous", or the window START as

  • updown_divergence_rate

    How often two venues settled the SAME 15-minute crypto window differently, over every settled window on record. Compares polymarket.com (Chainlink TWAP) with Kalshi and with Polymarket US (both CF Benchmarks BRTI), and Kalshi with Polymarket US as the same-feed control. Per pair:

  • archive_evidence

    What did a web page say on a given date? Finds the archived capture of a URL nearest that date across the Internet Archive Wayback Machine, Common Crawl and Arquivo.pt, reads it, and returns the readable text (HTML stripped) with the capture timestamp, a link to the archived copy

  • archive_compare

    What changed on a web page between two dates? Resolves the archived capture nearest each date (Internet Archive Wayback Machine, Common Crawl, Arquivo.pt), extracts the readable text of both, and returns a text-level diff: the segments removed and added, a similarity score, and b

  • research_row

    Claygent-style per-row research: answer ONE question about ONE company and return a JSON object matching your output_schema, with every field wrapped in its own evidence — {value, evidence_url, quote, status}. status is NEVER self-reported by the model: "found" means this code in

  • classify_row

    Cheap categorization: given a company and a list of candidate labels, decide which labels apply — the most common GTM/AI usage shape (tagging a list by industry, ICP fit, etc.), one small model call. Same evidence contract as research_row: each label comes back {label, applies, e

  • pipeworx_trending

    What other AI agents are calling on Pipeworx right now. Returns the top tools, top packs, and total call volume over a recent window (24h, 7d, or 30d). Useful for: (1) discovering what data sources are hot for current events, (2) confirming a popular tool is the canonical choice

  • suggest_questions

    What can I ask Pipeworx? / what is Pipeworx good for? / what can you do? / give me ideas / show me examples / getting started / what data do you have? — the onboarding entry point for an agent that just connected and wants to know what is worth asking. Returns category-bucketed e

  • generate_llms_txt

    Generate a production-ready llms.txt file for any URL so AI crawlers (ChatGPT, Claude, Perplexity) can index the site cleanly. Fetches the page, extracts title/description/key links, and emits the standard llms.txt markdown format. Output is a single text blob ready to drop at si

  • ai_visibility_check

    Probe one or more LLMs for what they know about a business / brand / product / topic and score visibility (0-100) per model. Default model is Workers AI Llama-3.3-70b (free); pass `_apiKey` to also probe Anthropic (BYO key — you pay Anthropic directly for those calls). Returns pe

  • scan_competitor_ai_presence

    Compare AI visibility across multiple entities side-by-side. Probes each entity (your brand + N competitors) with ai_visibility_check, ranks by score, surfaces which is most/least recognized. Useful for competitive AI-marketing audits: "does Claude know about us as well as our co

  • pipeworx_feedback

    Tell the Pipeworx team something is broken, missing, or needs to exist. Use when a tool returns wrong/stale data (bug), when a tool you wish existed isn't in the catalog (feature/data_gap), or when something worked surprisingly well (praise). ONLY for tools served by this Pipewor

  • remember

    Save data the agent will need to reuse later — across this conversation or across sessions. Use when you discover something worth carrying forward (a resolved ticker, a target address, a user preference, a research subject) so you don't have to look it up again. Stored as a key-v

  • recall

    Retrieve a value previously saved via remember, or list all saved keys (omit the key argument). Use to look up context the agent stored earlier — the user's target ticker, an address, prior research notes — without re-deriving it from scratch. Scoped to your identifier (anonymous

  • forget

    Delete a previously stored memory by key. Use when context is stale, the task is done, or you want to clear sensitive data the agent saved earlier. Pair with remember and recall.

  • gu_statute

    Get the FULL TEXT of a section of the Guam Code Annotated (GCA) — Guam territorial law — by citation. "9 GCA 16.30" (or "9 GCA § 16.30") is Aggravated Murder Defined; "21 GCA 33101" is who may take an acknowledgment of a deed. Guam uses TWO citation styles depending on the title:

  • gu_search

    Search the Guam Code Annotated BY TOPIC or keyword rather than citation — "murder", "security deposit", "concealed weapon permit", "homestead". Matches against official section and chapter CATCHLINES (not full statutory body text — Guam does not publish a full-text search, and th

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account pipeworx-io, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • ✓ Pass

    Endpoint responds

    Responded in 626 ms (HTTP 200)

  • – Not applicable

    Sign-in with OAuth

    No sign-in needed

  • ✓ Pass

    No hidden instructions in tool descriptions

    Read 46 tool descriptions and found no hidden instructions to the AI

Compared with others in Search & AI memoryi

  • More stars than 0% of the other 7249 servers in this category
  • Published to the registry more recently than 88% of the other 7249 servers in this category
  • Basic checks equal to or better than 100% of the other 7249 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Guam Code safe?

It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: PIPEWORX_API_KEY

Does it run on my computer or in the cloud?

Either way works: install it on your computer or connect to the cloud version.

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.2.1) reached the registry 5 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Context7, Codebase Memory, Exa

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Context7

by upstash

Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.

Computer or cloud★ 64,224MITUpdated today
Install

Codebase Memory

by DeusData

Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.

Runs on your computer★ 48,148MITUpdated 20 days ago
Install

Exa

by exa-labs

Connect AI agents to Exa for web search, content fetching, and multi-step research.

Runs in the cloud★ 5,213MITUpdated last month
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

@pipeworx/guam-code

Guam Code Annotated (GCA) — Guam territorial statutes, by citation and by topic/keyword search. Keyless.

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

Tools

  • gu_statute(citation, title?) — full text of a GCA section by citation ("9 GCA 16.30" is Aggravated Murder Defined; "21 GCA 33101" is who may take an acknowledgment of a deed). Resolves the citation to its one chapter PDF, fetches it live, and extracts the text. title is only needed if not already embedded in citation.
  • gu_search(query, title?, limit?) — topic/keyword search over section and chapter catchlines (not full statutory prose — see below), optionally restricted to one Title (1-22).

Auth

Keyless.

Source and shape

The Compiler of Laws (Judiciary of Guam, col.guamcourts.gov) publishes the GCA as ~800 per-CHAPTER PDFs, linked from one static HTML page: 22 collapsible Title panels, each listing its Chapters. There is no per-title listing, no search API, and no site-wide section index (confirmed live) — the same gap mcps/north-dakota-code hit for the Century Code. That page is baked ONCE (title/chapter/catchline/PDF URL) by scripts/bake-index.mjs.

Unlike North Dakota, the GCA index page does not also enumerate every section. But every sampled chapter PDF opens with its own embedded table of contents — a run of § . . Catchline. headings — so scripts/bake-sections.mjs fetches all ~800 chapter PDFs once more and bakes a section-level catchline index (15,760 rows) from that TOC block. gu_search reads it; gu_statute never trusts it for the text it returns — it re-derives section boundaries fresh from the live PDF on every call.

Refresh path

Re-run both whenever the Compiler of Laws amends the GCA enough to be worth re-baking (run the chapter index first — the section bake reads it):

node mcps/guam-code/scripts/bake-index.mjs > mcps/guam-code/src/gu-index-data.ts

node --experimental-strip-types mcps/guam-code/scripts/bake-sections.mjs > mcps/guam-code/src/gu-section-data.ts

The section bake needs --experimental-strip-types because it imports the pack's own TypeScript extractor directly (no tsx/ts-node dependency in this repo) — nothing at runtime needs that flag, only this one offline script. Budget a few minutes: ~800 HTTP fetches at modest concurrency, as a courtesy to col.guamcourts.gov rather than because it rate-limits.

Both baked modules are combined by src/gu-baked-data.ts (a plain re-export) into the ONE data module workers/gateway/src/pack-baked-indexes.json points at for this pack — the gateway uploads its exports to KV at deploy and injects them as args._bakedIndex, never as a module-scope import (see index.ts's ensureIndex; fleet #2754 took the gateway down the one time a baked table was value-imported into every isolate).

Two citation conventions, both real

Newer, recodified titles (9 GCA, the Criminal & Correctional Code, adapted from the 1977 Model Penal Code) cite "chapter.section" with a dot — "9 GCA § 16.30" is Aggravated Murder. Older titles (e.g. 21 GCA Ch. 33, Proof and Acknowledgments of Instruments) concatenate chapter and a zero-padded section number with no separator — "21 GCA § 33101" is chapter 33, section

  1. gu_statute accepts either form (see parseGuCitation in

src/index.ts). The chapter/section boundary for the no-dot form is genuinely ambiguous from the digit string alone (chapter numbers vary in length); it is resolved by picking the longest known chapter number, for the given Title, that is a literal prefix of the citation — correct in every case sampled.

shared/src/pdf-text.ts needed real fixes — folded in, fork deleted (fleet #2904)

Guam's chapter PDFs originally defeated the shared extractor in ways it did not yet handle, and this pack was built the same week another pack (#2884, New Mexico) was independently editing that shared file — so the fixes initially lived in src/gu-pdf-extract.ts, a pack-local fork of shared/src/pdf-text.ts, with a loud header comment for whoever next touched the shared extractor to fold them in (nothing about them was Guam-specific). That fold-in happened in fleet #2904: the fork is gone, this pack now calls extractPdfText from @pipeworx/shared directly, and all three fixes below live in shared/src/pdf-text.ts itself, benefiting every other PDF pack (kentucky-code, north-dakota-code, wyoming-code, new-mexico-code), not just this one:

  1. Literal strings weren't routed through the font decoder. Guam's producer (Neevia Document Converter, from Word) writes some non-WinAnsi subset fonts' text as parenthesized LITERAL strings ((abc)Tj) rather than hex (<...>Tj). The shared extractor's decodeRun passed a literal run through unchanged — correct for WinAnsi, but for these fonts the raw bytes are a tiny, arbitrary code space meaningful only via the font's own /ToUnicode CMap, which the shared code already had the machinery for (built for North Dakota) but only wired to the HEX-string path. Confirmed live: unfixed, § 16.10 extracted as control-character noise; fixed, it reads correctly.
  2. A declared `/Length` a few bytes long. Several older chapter PDFs ("MS Word for Windows Document" producer — an earlier era than the Neevia-converted ones above) declare a /Length 1+ bytes longer than their actual deflate stream. Python's zlib tolerates the trailing byte silently; Node/Workers' strict DecompressionStream throws ERR_TRAILING_JUNK_AFTER_STREAM_END. Now retried with the stream's tail trimmed a byte at a time (up to 4) before giving up.
  3. Crash-adjacent, found while baking the section index. The shared inflate() helper's two stream writes were fire-and-forget (void writer.write(...)); a malformed deflate stream (the same PDFs #2 above describes) rejected that promise as an UNHANDLED rejection, invisible to any caller's try/catch and fatal to the whole process — crashed scripts/bake-sections.mjs outright, mid-run. Fixed by attaching a no-op .catch() to each write/close; the real failure still surfaces through reader.read(), which the caller already handles.

One delta stayed pack-local, in `src/gu-font-cmap-fix.ts`, because it genuinely IS Guam-specific: one embedded symbol font per chapter PDF (...+WPTypographicSymbols, used only for curly quotes) carries a /ToUnicode CMap that maps its two codes to U+0041 ('A') and U+0040 ('@') instead of the left/right curly quote it visually renders as. Confirmed by eye: "ADirector of Public Safety@" in raw extraction is "“Director of Public Safety”" with those two codes substituted back — the obviously intended reading, reproduced by any PDF viewer's own copy-paste. This is a defect in Guam's own published PDF, not something a general-purpose extractor could derive, so it is passed into extractPdfText via its new fontCMapOverride option — a generic hook (match a font's own dictionary text, optionally return a replacement /ToUnicode map) with nothing Guam-specific about the mechanism itself, available to any future pack that hits a similarly broken source PDF.

Four capabilities — two available, two are not

  • Citation lookup — available (gu_statute).
  • Topic/keyword search — available (gu_search), over official CATCHLINES (section + chapter name), not full statutory prose. Coverage is best-effort: catchlines are derived from each chapter PDF's own table of contents rather than a separate official index, so an unusually formatted chapter can be under-represented.
  • Amendments/enactment history — embedded in gu_statute's text field as the statute's own "SOURCE:" line (e.g. "Enacted 1977 as 16.30; amended by P.L. 14-125..."), not split out as a separate field — the GCA does not mark it up distinctly enough to parse reliably across both PDF eras sampled.
  • Historical version (a section's text as it read before an amendment) — not available. col.guamcourts.gov serves the current text only; no per-year or per-session archive was found.

Known rough edge: page-furniture noise at a chapter's last section

gu_statute strips the repeating running header ("9 GCA CRIMES AND CORRECTIONS CH. 16 CRIMINAL HOMICIDE 1") and the "COL " stamp every page carries, self-derived from the chapter text's own first occurrence. Older-era PDFs (the "MS Word for Windows Document" producer, #2 above) sometimes extract that header with no inter-word spacing ("21GCAREAL PROPERTY" rather than "21 GCA REAL PROPERTY"), which the stripping regex — anchored on GCA preceded by whitespace — does not match. The statutory text itself is unaffected; only a section that happens to be the LAST one on a page, in one of these older chapters, can carry a trailing fragment of the next page's header/footer. Cosmetic, not a correctness defect.

Citations

Give citation as "9 GCA 16.30", "9 GCA § 16.30", "21 GCA 33101", or a bare section ("16.30" / "33101") with title passed separately.

Data sources

  • https://col.guamcourts.gov/guam-code-annotated/guam-code-annotated — the Title/Chapter index (one collapsible page). Baked once into src/gu-index-data.ts; never fetched per call.
  • https://col.guamcourts.gov/sites/default/files/9gc016.pdf — one chapter's full statutory text (here, 9 GCA Chapter 16, Criminal Homicide — swap the filename for any other chapter). gu_statute fetches this live on every call and extracts the target section out of it. The same ~800 chapter PDFs are also fetched once, offline, by scripts/bake-sections.mjs to build the catchline search index.

Both are plain, keyless, server-rendered HTML/PDF — no login, no JS, no rate-limit observed during development.

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{

"mcpServers": { "guam-code": { "url": "https://gateway.pipeworx.io/guam-code/mcp" } } }

What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/guam-code/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — ask_pipeworx, discover_tools, search_within, remember/recall and the rest of the gateway-wide set. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's initialize response states its exact scope, and is the authoritative answer for a given day.

This is deliberate, not multiplexing by accident. The meta-tools are what let a scoped connection answer a question this pack does not cover — via ask_pipeworx, which routes across the whole catalog — without you adding a second MCP server. There is currently no way to mount a pack endpoint without them; if the extra schemas cost you more context than the routing is worth, connect to the full gateway once rather than to several pack endpoints.

Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:

{

"mcpServers": { "pipeworx": { "url": "https://gateway.pipeworx.io/mcp" } } }

Both URLs reach the same gateway and the same 1865+ data sources. The only difference is which pack's tools are listed directly; ask_pipeworx reaches all of them from either one.

No MCP client? Call it over HTTP

curl -X POST https://gateway.pipeworx.io/v1/tools/gu_statute \

-H 'Content-Type: application/json' \ -d '{"citation":"9 GCA 16.30"}'

No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/gu_statute. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with `{"query":"..."}

Only the beginning is shown; read the rest in the repo

Ask PopNx