West Virginia Rules
NPM · @PIPEWORX/MCP-WEST-VIRGINIA-RULES · 2 COMPONENTS
West Virginia Code of State Rules (CSR) -- the state's administrative rules.
Available components
Last scanned (4 hours ago)
Scores higher than 72% of npm servers
Category Education and Research
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-west-virginia-rules). 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 Usability64
- AI-judged instruction clarity (excellent).Pass
- 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. 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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
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.
- 2 Nov 26 +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.
- 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.
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-west-virginia-rules@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-west-virginia-rules |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-west-virginia-rules/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3561055402 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:f37c3b28271737db31637744da046b3625327e55f29d399300145dc0c0b727464fc28582900a39e0467a7b20fc3c0f492adb59cd222c50425bc167b8c |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
get_rule ~135
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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". |
No output schema declared.
No examples provided.
read_rule_text ~193
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.
| Name | Type | Req | Description |
|---|---|---|---|
| doc_id | number | yes | 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). |
No output schema declared.
No examples provided.
search_rules ~379
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
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.
npm · @pipeworx/mcp-west-virginia-rules
claude mcp add pipeworx-io-west-virginia-rules -- npx -y @pipeworx/mcp-west-virginia-rules
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.