# Guam Code [Health: Active]

**Category:** ⚖️ Legal  
**Repository:** https://github.com/pipeworx-io/mcp-guam-code  
**GitHub Stars:** 0  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/guam-code

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

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "guam-code": {
    "command": "npx",
    "args": ["-y","@pipeworx/mcp-guam-code"]
  }
}
```

## Documentation

## What Guam Code MCP server does

Guam Code MCP server provides agent access to the Guam Code Annotated (GCA), the published collection of Guam territorial statutes. It supports two operations: retrieving a statute by citation and searching an index of section and chapter catchlines. The source material comes from chapter PDFs published by the Compiler of Laws of the Judiciary of Guam at `col.guamcourts.gov`.

The integration is keyless, so the supplied material does not describe an API token or other credential requirement. It is an independent, unofficial integration and is not affiliated with, endorsed by, or published by the upstream provider.

## How it works

For a citation request, Guam Code MCP server identifies the relevant title and chapter, fetches that chapter PDF live, and extracts the requested section. It accepts newer citation styles such as `9 GCA 16.30` and older concatenated forms such as `21 GCA 33101`. For the latter format, the resolver uses the longest known chapter number that is a literal prefix of the supplied section number.

Search uses a baked section-level index containing catchlines derived from chapter PDF tables of contents. The index covers section and chapter names rather than the full statutory prose, so a keyword search is not equivalent to searching every word in the law. Searches can optionally be limited to a Title from 1 through 22.

The source site organizes the GCA across roughly 800 chapter PDFs. The project creates its indexes offline, while statute text is re-derived from the live PDF for each lookup. This separates discovery from the returned statutory text and allows the lookup path to use the current source document.

## Tools and capabilities

Guam Code MCP server exposes these tools:

- `gu_statute(citation, title?)` returns the full text of a GCA section. The optional `title` helps when the title is not already included in the citation.
- `gu_search(query, title?, limit?)` searches section and chapter catchlines. `title` can restrict results to one GCA Title, and `limit` controls the result count.

A statute response can include the source line containing enactment and amendment information in its `text` field. That history is not returned as a separate structured field because the source PDFs do not mark it consistently enough across both PDF eras.

## Limitations and notes

The Guam Code MCP server returns the current text served by the Compiler of Laws. It does not provide historical versions of sections before amendments, and no per-year or per-session archive is described.

Search coverage is best-effort. Because catchlines are extracted from each chapter PDF's embedded table of contents, unusually formatted chapters may be incompletely represented. Searches also do not inspect the full statutory prose.

Some older PDFs can leave page-furniture noise around the final section on a page, including a running header with missing spaces. The statutory text itself is described as unaffected. The extractor also contains handling for Guam PDF font mappings and malformed compression metadata, including a Guam-specific correction for curly quotation marks.

_Full upstream README: https://allmcps.com/mcp/guam-code/readme_