# Puerto Rico Code (npm · @pipeworx/mcp-puerto-rico-code)

Puerto Rico statutes — 'leyes' (acts) of the Puerto Rico Legislature, section/article lookup and…

- Trust score: 82/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 84/100, [markdown](https://verifymcp.io/servers/pipeworx-io-puerto-rico-code/puerto-rico-code-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-puerto-rico-code/puerto-rico-code-mcp)
- npm · `@pipeworx/mcp-puerto-rico-code`: 82/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-puerto-rico-code/pipeworx-mcp-puerto-rico-code.md), [page](https://verifymcp.io/servers/pipeworx-io-puerto-rico-code/pipeworx-mcp-puerto-rico-code)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-puerto-rico-code`
- Version: `0.2.1`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-puerto-rico-code).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 0 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 61/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 618 tokens (~309/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Puerto Rico Code MCP server?

Puerto Rico Code runs locally as an npm package, launched with npx -y @pipeworx/mcp-puerto-rico-code. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add pipeworx-io-puerto-rico-code -- npx -y @pipeworx/mcp-puerto-rico-code
```

### Cursor

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

### VS Code

```json
{
  "servers": {
    "pipeworx-io-puerto-rico-code": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-puerto-rico-code"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-puerto-rico-code -- npx -y @pipeworx/mcp-puerto-rico-code
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-puerto-rico-code": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-puerto-rico-code"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-puerto-rico-code --command npx --arg -y --arg @pipeworx/mcp-puerto-rico-code
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-puerto-rico-code:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-puerto-rico-code"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-puerto-rico-code": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-puerto-rico-code"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-puerto-rico-code -t stdio -c npx -a -y @pipeworx/mcp-puerto-rico-code
```

### Other

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

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-04 (score 81, +3)

- [security regression] Tool safety: pass → unverified
- [security] Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional improvement] Stability: unverified → 0.20
- [functional] First check of Schema quality: unverified
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-10-31 (score 78, 0)

- [functional regression] Security disclosure: unverified → fail

### 2026-10-29 (score 78)

First indexed and scored.

## MCP tools (2)

### `pr_statute` (~341 tokens)

Get the text of a Puerto Rico "ley" (act) by citation — accepts an LPRA citation like "33 LPRA 5001" (33 L.P.R.A. § 5001, the Penal Code's murder-related provisions title) or "31 LPRA 5311" (the Civil Code), OR a direct act number like "146-2012" (optionally with an article, e.g. "146-2012 Art. 92"). LPRA citations resolve ONLY for the LPRA títulos this pack has verified map to one specific act by reading that act's own text (currently Título 31, Código Civil de Puerto Rico de 2020; and Título 33, Código Penal de Puerto Rico de 2012) — most of LPRA's ~35 títulos aggregate many acts and are NOT yet mapped; for those, look up the specific "ley" by its own number instead. Returns the article/section heading and FULL SPANISH TEXT AS PUBLISHED by the Oficina de Gerencia y Presupuesto (OGP) — never machine-translated — plus the source PDF URL and data_as_of. Spanish statute citations and vocabulary: artículo, ley, código, estatuto, derecho puertorriqueño, Leyes de Puerto Rico Anotadas.

Input parameters:

- `citation` (string, required): An LPRA citation ("33 LPRA 5001", "31 L.P.R.A. § 5311"), or an act number alone or with an article ("146-2012", "146-2012 Art. 92", "Ley 55-2020 Artículo 1").

### `pr_search` (~219 tokens)

Search Puerto Rico statutes by topic or keyword in Spanish (e.g. "homicidio", "arrendamiento", "violencia doméstica", "contratos"). Searches two tiers: REAL full-text search over the article bodies of the two LPRA-mapped consolidated codes (Código Penal / Código Civil — real body-text matches, not just catchlines), plus a title/catchline search over OGP's full catalog of ~15,500 published "leyes" (acts) for topics outside those two codes. Each result is labelled result_type "lpra_section" (a real statute section, with its LPRA citation) or "act" (an act title match — call pr_statute with its act number for the text). Keyless, Spanish text as published.

Input parameters:

- `limit` (number): Max results to return, default 10, max 30.
- `query` (string, required): Topic or keywords in Spanish, e.g. "arrendamiento" (lease) or "homicidio" (homicide).

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-puerto-rico-code/pipeworx-mcp-puerto-rico-code#diagnostics

## Score history

- 2026-11-05: 82
- 2026-11-04: 81
- 2026-11-03: 78
- 2026-11-02: 78
- 2026-11-01: 78
- 2026-10-31: 78
- 2026-10-30: 78
- 2026-10-29: 78

## Common questions

### What is the Puerto Rico Code MCP server?

Puerto Rico Code is an MCP server listed in the public MCP registry as io.github.pipeworx-io/puerto-rico-code. Puerto Rico statutes, 'leyes' (acts) of the Puerto Rico Legislature, section/article lookup and… This page covers its npm package (@pipeworx/mcp-puerto-rico-code).

### Is the Puerto Rico Code MCP server safe to use?

Puerto Rico Code scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Puerto Rico Code MCP server expose?

Puerto Rico Code exposes 2 tools: pr_statute, pr_search. Their descriptions and schemas cost roughly 560 tokens of context every time the server is loaded.

### Is the Puerto Rico Code MCP server still maintained?

Puerto Rico Code is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the Puerto Rico Code MCP server under?

Puerto Rico Code declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the Puerto Rico Code MCP server?

VerifyMCP ran 16 checks on Puerto Rico Code, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-puerto-rico-code
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-puerto-rico-code
- Repository: https://github.com/pipeworx-io/mcp-puerto-rico-code
- Website: https://pipeworx.io/packs/puerto-rico-code
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-puerto-rico-code/pipeworx-mcp-puerto-rico-code.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-puerto-rico-code/pipeworx-mcp-puerto-rico-code/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-puerto-rico-code/pipeworx-mcp-puerto-rico-code.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-puerto-rico-code/pipeworx-mcp-puerto-rico-code