# West Virginia Rules (npm · @pipeworx/mcp-west-virginia-rules)

West Virginia Code of State Rules (CSR) -- the state's administrative rules.

- Trust score: 82/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`: 65/100, [markdown](https://verifymcp.io/servers/pipeworx-io-west-virginia-rules/west-virginia-rules-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-west-virginia-rules/west-virginia-rules-mcp)
- npm · `@pipeworx/mcp-west-virginia-rules`: 82/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-west-virginia-rules/pipeworx-mcp-west-virginia-rules.md), [page](https://verifymcp.io/servers/pipeworx-io-west-virginia-rules/pipeworx-mcp-west-virginia-rules)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-west-virginia-rules`
- 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-west-virginia-rules).
  - 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**: 64/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 769 tokens (~256/item across 3 items; 3 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 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 West Virginia Rules MCP server?

West Virginia Rules runs locally as an npm package, launched with npx -y @pipeworx/mcp-west-virginia-rules. 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-west-virginia-rules -- npx -y @pipeworx/mcp-west-virginia-rules
```

### Cursor

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

### VS Code

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

### Codex

```bash
codex mcp add pipeworx-io-west-virginia-rules -- npx -y @pipeworx/mcp-west-virginia-rules
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add pipeworx-io-west-virginia-rules --command npx --arg -y --arg @pipeworx/mcp-west-virginia-rules
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-west-virginia-rules:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-west-virginia-rules"]
```

### Netclaw

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

### Vellum

```bash
assistant mcp add pipeworx-io-west-virginia-rules -t stdio -c npx -a -y @pipeworx/mcp-west-virginia-rules
```

### Other

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

## 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-04 (score 82, +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.

### 2026-11-02 (score 81, +1)

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

### 2026-10-31 (score 80, +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-30 (score 79, 0)

- [functional regression] Security disclosure: unverified → fail

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

First indexed and scored.

## MCP tools (3)

### `search_rules` (~379 tokens)

Search West Virginia administrative rules (Code of State Rules) -- the agency regulations that implement WV statutes, e.g. Board of Medicine physician-assistant supervision, nursing practice, professional-licensing requirements. Filter by agency (e.g. "Medicine", "Registered Nurses, WV Board of"), title-series (e.g. "11-01B"), rule-name words, authorizing WV Code citation (e.g. "30-3E-3"), or full text of the rule documents. At least one filter is required. Returns counts by status first, then matching rule versions (active rules first). Use for "what does West Virginia require for X" when the answer is an agency rule rather than a statute; pair with wv_code_section for the statute and read_rule_text for the rule text.

Input parameters:

- `agency` (string): Agency name as the register lists it, e.g. "Medicine", "Osteopathic Medicine", "Registered Nurses, WV Board of", "Physical Therapy".
- `authority` (string): Authorizing WV Code citation, e.g. "30-3E-3".
- `full_text` (string): Words to find inside the rule documents, e.g. "collaborative agreement".
- `full_text_mode` (string): any = any of the words (default); literal = exact phrase.
- `limit` (number): Rule versions to return (default 25, max 100). Counts always cover every match.
- `rule_name` (string): Words in the rule title, e.g. "physician assistants".
- `status` (string): Restrict by rule status. Omit for all versions (history included).
- `title_series` (string): Rule family, e.g. "11-01B" (title 11, series 01B = Board of Medicine physician assistants).

### `get_rule` (~135 tokens)

Get one West Virginia administrative rule family by title-series (e.g. "11-01B"): every version ever filed with its effective date, status (Active, Historical, Emergency), authorizing statute, and the filing history (modified/agency-approved/legislative-approval filings) with document ids that read_rule_text can open. Use after search_rules to see the current rule and what superseded it.

Input parameters:

- `document` (number): Optionally, a rule version document number from search_rules to list that version's filings instead.
- `title_series` (string): Rule family, e.g. "11-01B".

### `read_rule_text` (~193 tokens)

Read the text of a West Virginia administrative rule filing (the rule as filed). Takes a filing document id from get_rule. Returns the text in pages of characters with total length so long rules can be read in sequence via offset. Filings described "Modified File" are redlines (struck and inserted text both appear, e.g. old and new section numbers side by side); the "Agency Approved" and "Valid" filings are cleaner. Use to quote the exact supervision, scope-of-practice, or licensing requirement.

Input parameters:

- `doc_id` (number, required): Filing document id from get_rule, e.g. 59557.
- `find` (string): Optional: return the passages around this phrase instead of a linear page.
- `max_chars` (number): Characters to return (default 20000, max 40000).
- `offset` (number): Character offset to start from (default 0).

## Diagnostics

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

## Score history

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

## Common questions

### What is the West Virginia Rules MCP server?

West Virginia Rules is an MCP server listed in the public MCP registry as io.github.pipeworx-io/west-virginia-rules. West Virginia Code of State Rules (CSR) -- the state's administrative rules. This page covers its npm package (@pipeworx/mcp-west-virginia-rules).

### Is the West Virginia Rules MCP server safe to use?

West Virginia Rules 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 West Virginia Rules MCP server expose?

West Virginia Rules exposes 3 tools: search_rules, get_rule, read_rule_text. Their descriptions and schemas cost roughly 707 tokens of context every time the server is loaded.

### Is the West Virginia Rules MCP server still maintained?

West Virginia Rules 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 West Virginia Rules MCP server under?

West Virginia Rules 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 West Virginia Rules MCP server?

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