Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Washington Code

NPM · @PIPEWORX/MCP-WASHINGTON-CODE · 2 COMPONENTS

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

+3 this week 83 Trust /100

Last scanned (7 hours ago)

Scores higher than 76% of npm servers

Category Education and Research

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-washington-code). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 7 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability68
  • AI-judged instruction clarity (excellent).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
  • Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 5 Nov 26 +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.

  • 3 Nov 26 +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.

  • 31 Oct 26 +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.

  • 29 Oct 26 80

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Analysed npm/@pipeworx/mcp-washington-code@0.2.0

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo pipeworx-io/mcp-washington-code
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/pipeworx-io/mcp-washington-code/.github/workflows/publish.yml@refs/heads/main
Rekor log index 3561011540
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:659d62ee861e85fa7159e0990d56e5e8abcbbee0ff3bd6660c0f9523c1668db6d864bb5bcd88434ca57b43f2b22aaf60897b06ad207250d7e458e6f03

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 10 exposed · ~2,169 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
wa_bill_amendments ~218

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.

NameTypeReqDescription
bienniumstring–Washington biennium, e.g. "2025-26" or a year like "2026". Omit for the current biennium.
billstringyesBill number, with or without prefix: "HB 1002", "SB 5016", or bare "1002".

No output schema declared.

No examples provided.

wa_bill_status ~244

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.

NameTypeReqDescription
bienniumstring–Washington biennium, e.g. "2025-26" or a year like "2026". Omit for the current biennium.
billstringyesBill number, with or without prefix: "HB 1000", "SB 5016", "2SHB 1000", or bare "1000".

No output schema declared.

No examples provided.

wa_bill_votes ~184

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.

NameTypeReqDescription
bienniumstring–Washington biennium, e.g. "2025-26" or a year like "2026". Omit for the current biennium.
billstringyesBill number, with or without prefix: "HB 1002", "SB 5016", or bare "1002".

No output schema declared.

No examples provided.

wa_rcw_section ~162

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.

NameTypeReqDescription
sectionstringyesRCW citation, e.g. "9A.32.030" or "46.61.502". Title.chapter.section.

No output schema declared.

No examples provided.

wa_session_bills ~322

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.

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

No output schema declared.

No examples provided.

wa_wac_archived_section ~224

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.

NameTypeReqDescription
sectionstringyesWAC section citation, e.g. "296-800-110".
yearnumberyesArchive year, 2004–last year. Full text for 2019 onward; PDF-only before that.

No output schema declared.

No examples provided.

wa_wac_browse ~163

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.

NameTypeReqDescription
citestring–Omit for all titles; a title number ("296") for its chapters; a chapter ("296-800") for its sections.

No output schema declared.

No examples provided.

wa_wac_filings ~156

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.

NameTypeReqDescription
citestringyesWAC section ("296-800-110") or chapter ("296-800").

No output schema declared.

No examples provided.

wa_wac_search ~229

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.

NameTypeReqDescription
cite_prefixstring–Optional WAC title or chapter to restrict results to, e.g. "296" or "296-800".
limitnumber–Max results to return, default 10, max 25.
querystringyesTopic or keywords, e.g. "safety bulletin board" or "landlord deposit". Plain words; the index is Elasticsearch-style (all terms, stemmed).

No output schema declared.

No examples provided.

wa_wac_section ~267

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.

NameTypeReqDescription
sectionstringyesWAC 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").

No output schema declared.

No examples provided.

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.

npm · @pipeworx/mcp-washington-code

# add to Claude Code
claude mcp add pipeworx-io-washington-code -- npx -y @pipeworx/mcp-washington-code
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.