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.

Hawaii Code

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

Hawaii Revised Statutes — state statutes by citation, by topic, and (where the Legislature itself…

+3 this week 82 Trust /100

Last scanned (4 hours ago)

Scores higher than 72% 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-hawaii-code). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 2 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability63
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 518 tokens (~259/item across 2 items; 2 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 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.

  • 4 Nov 26 +1

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

  • 3 Nov 26 +27
    • Known CVEs: unverified → pass ▲ security
    • Malware scan: unverified → pass ▲ security
    • Dependency health: unverified → pass ▲ functional
  • 2 Nov 26 −26
    • Malware scan: pass → unverified ▼ security
    • Known CVEs: pass → unverified ▼ security
    • Dependency health: pass → unverified ▼ functional
    • Package version: 0.2.0 → 0.2.1 functional
  • 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.

  • 30 Oct 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 29 Oct 26 79

    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-hawaii-code@0.2.1

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-hawaii-code
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/pipeworx-io/mcp-hawaii-code/.github/workflows/publish.yml@refs/heads/main
Rekor log index 3637388693
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:ef5f3b97b84a52fe246282cf05660b98b7a1c29c4795ad570c09bd19184393524dab453728d28997f8059a2030d8bd63cc5044d372ea3ac4f63ae0184

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 · 2 exposed · ~463 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
hi_search ~173

Search the Hawaii Revised Statutes BY TOPIC or keyword rather than citation — "landlord security deposit", "concealed firearm permit", "murder". Matches against the Legislature's own official section and chapter CATCHLINES across the whole Code (not full statutory prose — Hawaii does not publish a full-text search of statute body text, verified live), e.g. "landlord" surfaces sections like "Landlord's remedies for failure by tenant to pay rent" under chapter 521 (Residential Landlord-Tenant Code). Returns matching citations and catchlines; call hi_statute with a citation for the full text. Keyless.

NameTypeReqDescription
limitnumber–Max results to return, default 10, max 25.
querystringyesTopic or keywords, e.g. "landlord security deposit".

No output schema declared.

No examples provided.

hi_statute ~290

Get the FULL TEXT of a section of the Hawaii Revised Statutes (HRS) — Hawaii state law — by citation. "707-701" is murder in the first degree; "521-44" is a landlord's security-deposit duty under the Residential Landlord-Tenant Code. Accepts natural forms: "707-701", "HRS 707-701", "§707-701". Returns the current statutory text, the official catchline, chapter context, and amendment/enactment history parsed from the Legislature's own "[L 1972, c 9, ...]" session-law bracket. Pass "year" (1999-2025) to get that year's historical archived text of the same section instead of the current one — Hawaii publishes a full year-by-year online archive. Keyless. Use for "what does HRS 707-701 say" or to check a Hawaii statute a case or lease relies on, now or as of a past year.

NameTypeReqDescription
citationstringyesSection citation, chapter-section, e.g. "707-701" (murder) or "521-44" (security deposits). Some sections carry a decimal suffix, e.g. "521-69.5".
yearnumber–Optional: a historical year (1999-2025) to fetch that year's archived text instead of the current one.

No output schema declared.

No examples provided.

Install

How do I install the Hawaii Code MCP server?

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

# add to Claude Code
claude mcp add pipeworx-io-hawaii-code -- npx -y @pipeworx/mcp-hawaii-code
Common questions

What is the Hawaii Code MCP server?

Hawaii Code is an MCP server listed in the public MCP registry as io.github.pipeworx-io/hawaii-code. Hawaii Revised Statutes, state statutes by citation, by topic, and (where the Legislature itself… This page covers its npm package (@pipeworx/mcp-hawaii-code).

Is the Hawaii Code MCP server safe to use?

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

Hawaii Code exposes 2 tools: hi_statute, hi_search. Their descriptions and schemas cost roughly 463 tokens of context every time the server is loaded.

Is the Hawaii Code MCP server still maintained?

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

Hawaii 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.