# Washington Code (npm · @pipeworx/mcp-washington-code)

Washington state law: the Revised Code of Washington (RCW, statutes), the Washington…

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

## Components

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

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-washington-code`
- Version: `0.2.0`
- 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-washington-code).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 7 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 68/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2223 tokens (~222/item across 10 items; 10 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 10 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 11 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 Washington Code MCP server?

Washington Code runs locally as an npm package, launched with npx -y @pipeworx/mcp-washington-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-washington-code -- npx -y @pipeworx/mcp-washington-code
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-washington-code": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-washington-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 83, +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-03 (score 82, +1)

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

### 2026-10-31 (score 81, +1)

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

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

First indexed and scored.

## MCP tools (10)

### `wa_rcw_section` (~162 tokens)

Get the FULL TEXT of a section of the Revised Code of Washington (RCW) — Washington state STATUTES — by citation. "RCW 9A.32.030" is first degree murder. Returns the statutory text and its heading. Keyless. Use for "what does RCW 46.61.502 say", "text of RCW 49.60.180", or to check a Washington statute a case relies on. For agency RULES (Washington Administrative Code, citations like "WAC 296-800-110") use wa_wac_section instead.

Input parameters:

- `section` (string, required): RCW citation, e.g. "9A.32.030" or "46.61.502". Title.chapter.section.

### `wa_wac_section` (~267 tokens)

Get the CURRENT FULL TEXT of a section of the Washington Administrative Code (WAC) — Washington state agency RULES / regulations — by citation. "WAC 296-800-110" is L&I's safe-workplace summary; "458-20-178" is the Department of Revenue use-tax rule. Returns the rule text, its caption, the statutory-authority history (every WSR filing that amended it, with filed/effective dates) and the RCW sections the agency cited as authority. A repealed or nonexistent section is reported as found:false (the site redirects it). Keyless. Use for "what does WAC 296-800-110 say", "text of WAC 388-76-10000", or to check a Washington regulation an agency decision cites. For STATUTES (RCW) use wa_rcw_section; for past years use wa_wac_archived_section; to search by topic use wa_wac_search.

Input parameters:

- `section` (string, required): WAC citation, title-chapter-section, e.g. "296-800-110" or "WAC 458-20-178". Chapter and title parts may carry a letter suffix ("296-14A-100", "132C-120-010").

### `wa_wac_search` (~229 tokens)

Search the FULL TEXT of the Washington Administrative Code (WAC) by topic or keyword — "workplace safety bulletin board", "security deposit", "septic system permit", "cannabis retailer". Calls the Washington State Legislature's own full-text search index of every WAC section (it matches rule TEXT, not just captions), returns matching citations with captions, highlighted snippets and the index-wide match count. Optionally restrict to a title or chapter with cite_prefix ("296" for L&I, "458-20" for Revenue excise-tax rules). Call wa_wac_section with a citation for the full text and history. Keyless.

Input parameters:

- `cite_prefix` (string): Optional WAC title or chapter to restrict results to, e.g. "296" or "296-800".
- `limit` (number): Max results to return, default 10, max 25.
- `query` (string, required): Topic or keywords, e.g. "safety bulletin board" or "landlord deposit". Plain words; the index is Elasticsearch-style (all terms, stemmed).

### `wa_wac_browse` (~163 tokens)

Browse the structure of the Washington Administrative Code (WAC): with no cite, lists every WAC TITLE with the agency it belongs to (Title 296 = Labor and Industries, 458 = Revenue, 388 = Social and Health Services, 173 = Ecology, 246 = Health); with a title ("296") lists its CHAPTERS with captions; with a chapter ("296-800") lists its SECTIONS with captions and subheadings. Use to find which chapter covers a topic before calling wa_wac_section, or to enumerate every rule in a chapter. Keyless.

Input parameters:

- `cite` (string): Omit for all titles; a title number ("296") for its chapters; a chapter ("296-800") for its sections.

### `wa_wac_archived_section` (~224 tokens)

Get the text of a Washington Administrative Code (WAC) section AS IT STOOD at the end of a PAST YEAR, from the Legislature's annual WAC archive. Year-end snapshots with full text for 2019 onward (e.g. "WAC 296-800-110 in 2020"); 2004–2018 are PDF-only and the tool returns the chapter PDF link for 2016–2018 and the archive directory for earlier years rather than text. Returns the archived text, caption and the history line as printed that year, so you can diff it against wa_wac_section (current). Keyless. Use for "what did WAC 314-55-010 say in 2021", or to check which version of a rule applied on a date.

Input parameters:

- `section` (string, required): WAC section citation, e.g. "296-800-110".
- `year` (number, required): Archive year, 2004–last year. Full text for 2019 onward; PDF-only before that.

### `wa_wac_filings` (~156 tokens)

List the Washington State Register (WSR) rule-making FILINGS that affected a Washington Administrative Code (WAC) section or chapter — the amendment history as agency actions: WSR number, filing type (Permanent Rule, Proposal Original Notice, Emergency Rule, Expedited Rule Making, Preproposal Statement of Inquiry…), date filed, and a link to the filing text. Newest first. Use for "when was WAC 296-800-110 last amended", "is there a pending proposal to change chapter 458-20 WAC", or to trace a rule's rule-making record. Keyless.

Input parameters:

- `cite` (string, required): WAC section ("296-800-110") or chapter ("296-800").

### `wa_bill_status` (~244 tokens)

Get the current status of a Washington State LEGISLATIVE BILL — its description, legal title, sponsor(s), introduced date, procedural history line and current status (e.g. "H Rules X", "Passed Legislature"), and companion bills in the other chamber. Reads directly from the Washington State Legislature's own bill-tracking service (not a third-party aggregator). Use for "what is the status of HB 1000", "who sponsored SB 5016", "is HB 1002 still active". Bill numbers reset each biennium (default: the current one) — pass biennium for a past session. Keyless. For an amendment history use wa_bill_amendments; for floor votes use wa_bill_votes; for everything introduced in a session use wa_session_bills.

Input parameters:

- `biennium` (string): Washington biennium, e.g. "2025-26" or a year like "2026". Omit for the current biennium.
- `bill` (string, required): Bill number, with or without prefix: "HB 1000", "SB 5016", "2SHB 1000", or bare "1000".

### `wa_bill_amendments` (~218 tokens)

List the AMENDMENTS proposed to a Washington State legislative bill — amendment name/drafting number, sponsor (member or committee), type (floor/committee), description, floor action (ADOPTED/FAILED/WITHDRAWN) and date, with links to the amendment text. Returns the most recent amendment first and a count by floor action. Reads directly from the Washington State Legislature's own bill-tracking service. Use for "what amendments have been offered to HB 1002", "was the striker amendment adopted on SB 5016". A bill with no amendments on file returns an empty list, not an error. Keyless. For the bill's overall status use wa_bill_status.

Input parameters:

- `biennium` (string): Washington biennium, e.g. "2025-26" or a year like "2026". Omit for the current biennium.
- `bill` (string, required): Bill number, with or without prefix: "HB 1002", "SB 5016", or bare "1002".

### `wa_bill_votes` (~184 tokens)

Get the recorded FLOOR ROLL-CALL VOTES on a Washington State legislative bill — chamber, motion ("3rd Reading & Final Passage"), date, and yea/nay/absent/excused counts with the voting legislators named in each category. Most recent vote first. Reads directly from the Washington State Legislature's own bill-tracking service. Use for "how did the House vote on HB 1002", "did SB 5016 pass the Senate". Voice votes and committee-only votes are not recorded here. Keyless.

Input parameters:

- `biennium` (string): Washington biennium, e.g. "2025-26" or a year like "2026". Omit for the current biennium.
- `bill` (string, required): Bill number, with or without prefix: "HB 1002", "SB 5016", or bare "1002".

### `wa_session_bills` (~322 tokens)

List Washington State legislative bills for a BIENNIUM filtered by procedural status: "introduced" (every bill filed, default), "passed_house", "passed_senate", "passed_legislature", "signed" (by the Governor), "vetoed", or "partial_veto" (the last three require agency: "House" or "Senate", the chamber of origin). Returns aggregate counts (by chamber, by type, active count) first, then a page of bare bill records (id, type, chamber, active) — call wa_bill_status on an id for its description. Reads directly from the Washington State Legislature's own bill-tracking service. Use for "how many bills passed the Legislature in 2025-26", "what did the Governor sign from the House in 2025-26". Keyless.

Input parameters:

- `agency` (string): Chamber of origin, "House" or "Senate" — required for status signed/vetoed/partial_veto.
- `biennium` (string): Washington biennium, e.g. "2025-26" or a year like "2026". Omit for the current biennium.
- `limit` (number): Max records to return, default 15, max 50.
- `offset` (number): Pagination offset into the full result set, default 0.
- `status` (string): One of: introduced (default), passed_house, passed_senate, passed_legislature, signed, vetoed, partial_veto.

## Diagnostics

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

## Score history

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

## Common questions

### What is the Washington Code MCP server?

Washington Code is an MCP server listed in the public MCP registry as io.github.pipeworx-io/washington-code. Washington state law: the Revised Code of Washington (RCW, statutes), the Washington… This page covers its npm package (@pipeworx/mcp-washington-code).

### Is the Washington Code MCP server safe to use?

Washington Code scores 83 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 Washington Code MCP server expose?

Washington Code exposes 10 tools: wa_rcw_section, wa_wac_section, wa_wac_search, wa_wac_browse, wa_wac_archived_section, and 5 more. Their descriptions and schemas cost roughly 2,169 tokens of context every time the server is loaded.

### Is the Washington Code MCP server still maintained?

Washington 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 Washington Code MCP server under?

Washington 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 Washington Code MCP server?

VerifyMCP ran 16 checks on Washington 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-washington-code
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-washington-code
- Repository: https://github.com/pipeworx-io/mcp-washington-code
- Website: https://pipeworx.io/packs/washington-code
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-washington-code/pipeworx-mcp-washington-code.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-washington-code/pipeworx-mcp-washington-code/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-washington-code/pipeworx-mcp-washington-code.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-washington-code/pipeworx-mcp-washington-code